In my previous post, I provided some context for how this project came to fruition. In this entry, I’ll share the process and my thoughts on the exercise, as well as the outcome.
Let’s dig in.
Prerequisites
For starters, a WordPress.com account is needed to use Telex. Naturally. I simply logged-in with no issues.
Next, everything takes place in the WP admin block editor within a Playground instance. I think that some familiarity with this area of WordPress, along with plugins and blocks, are expected and certainly helpful.
But unlike the block editor in a WordPress install, the ability to instantly toggle between Editor, Frontend, and Admin is awesome. That, and the toggle between Preview and Code.
Can we please get this into core Release 7.1?
The Enhanced Prompt
Staring at the blinking cursor awaiting my instructions gave me Commodore 64 vibes. That might be intentional, especially with a throwback name like Telex.
I didn’t, but if I had read the FAQs first, I would’ve learned that the instructions were to use natural language and be as descriptive as possible. Problem was, I didn’t know in detail what I needed. The starting picture was clear in my head. But the words to describe the outcome was a little elusive. And I was a little lazy, too.
But I needed to just get on with it. There was zero risk involved here.
My instinct was to treat it like a search engine and type in some keywords. So that’s what I did. But just before hitting the ‘BUILD’ button, I noticed the ‘ENHANCE PROMPT’ option. Zero risk, right?
Ok, this thing just read my mind.
Click ‘BUILD’
Speed
It probably took Telex around 1-2 minutes max before generating a Playground instance of WordPress with the freshly pressed block installed and activated. That is lightning fast.
How long would this have taken a developer to do by hand?
Eureka!
It took me a few moments to stare at my screen and take in what had just happened. And to figure out what comes next.
Using the dialogue from “Who’s on First?“ I spent the next few minutes creating a couple of Question and Answer options, saving it, then previewing the page on the front end.
This was my eureka moment. It works!
I played and tested it some more, finding out how things worked between the front and back ends. This is the point where a light came on.
Tweaks & Iterations
I really didn’t know exactly what I wanted in my block with my first prompt. But once I had something tangible to push and pull around, those gaps were getting filled in.
Of the 3-4 hours I spent creating the block, 90% of that time was spent fine-tuning, styling, adding features and functionality. With each iteration, a new improvement presented itself
This brings to mind several other ‘zero risk’ features built into Telex.
- Version Control – Each new prompt creates a new version of the block/plugin. The versions are recursive, so you can go back and restore a version if you find yourself down a road you no longer want to travel.
- Downloads – At any time, you can download the project as a plugin. Should things go awry, simply reinstall the project. Furthermore, the zip file created is the same file used to install as a plugin on any other WordPress site.
- Remix – Similar to the version control feature, the remix command allows you to get to a certain point and essentially fork the project into a new one. While the Remixed project contains all the files of the version being remixed, the prompt window gets a clean slate.
- Saved to Telex – Projects and prompts are stored in Telex in their latest version. Picking up right where you left off and having the ability to go back and review prompts to the beginning is extremely helpful and convenient.
At the time of this post, there are currently 26 versions of Socratic Diagnostic. The 27th prompt involved a security and compatibility code audit. No changes were made.
Socratic Diagnostic: How it works
The easiest way to demonstrate my plugin would be to install, activate, and add it right here below this sentence. And I’m extremely confident it would work.
But for now, I’d much rather it be experienced within Telex. So go check it out.
Tips & Tricks
- It helps to have your flowchart outlined before beginning. Even if it’s just a few questions. Think like a support technician similar to your mechanic or doctor who is trying to narrow down the issue through a series of questions. If you begin with the end in mind as Dr. Covey advises, it’ll be much easier to create and map your diagnostic questions.
- Some answers can be used more than once. Use the ‘Duplicate‘ and ‘Move‘ buttons for faster questionnaire creation. Question cards can be moved within or between levels.
- Use the Tree Preview tab next to the Tree Editor to keep track of the questionnaire path as more questions and levels are added. Each level is color coded to help with this as well.
- Save the page before previewing the Frontend. You’ll be warned anyway.
Final Thoughts
Going through this exercise unlocked something new in my mind. While I am still likely to search out existing solutions for most issues, I now know there is yet another valuable tool in the toolbox.
In fact, I’ve already started another Telex block project.
One of the things that I didn’t realize was happening until going back to read my prompts, was that I was learning how to describe what I wanted in words. I didn’t use my voice to speak to the AI Assistant, but my prompts became more conversational, rather than just inputting keyword entries.
When it comes to AI builders, the talk among techies is that these types of tools will render developers obsolete. Perhaps some, but not all. The technology is unbelievably smart and efficient. But it is still learning.
For the world that I navigate, I can’t help but see a parallel with the way that many small business owners already approached their websites. That is, spinning up a WordPress website is easy and free. Easier with AI? I’m not sure. Maybe if you know what you want.
But the question inevitably becomes, “Now what?”
Who’s going to maintain this?
Add features and functionality?
Patch security vulnerabilities?
Ensure compatibility with core, php version, themes, etc?
Business owners want to run their businesses, not tinker with websites and AI builders.
As you can see, I am left with a bunch of questions. More than can be addressed here, and some of which go beyond the scope of creating for and with WordPress. But those questions above, the ones clients are concerned about, those are the motivation for my last prompt. Version 27. A code audit.
Is it safe? Is it clean? Is it buggy or optimal?
Perhaps this is the next area of deeper exploration.
You must be logged in to post a comment.