If you’re a software engineer like me, the first few months of 2026 were incredible.
Coding agents suddenly became good enough that we no longer needed to manually write code.
But if you’re like me, then sometime later you hit a wall.
The honeymoon period ended, and the novelty wore off.
No more dopamine hits.
It’s August, and I feel utterlyfatigued.
To be honest, I’m sick to death of writing longform English to describe every change I want to my codebase.
However, I also don’t want to go back to writing all my code manually.
There was real tedium in that practice that I’d prefer to avoid for…well, the rest of my life.
And yet, I sense that Ineedto have better insight and control over what my code is doing.
I want to know that my output is high quality, reliable software.
I want to feel good about myself as a professional.
So I’m trying to find a way to have my cake and eat it too.
My problem with coding agents is that
With coding agents, prompts are (a) longform, (b) imperative, and (c) transient.
With Huzzah, prompts are (a) pseudocode, (b) declarative, and (c) persistent.
Your browser does not support embedded video. You can
watch the Huzzah demonstration directly
Let’s take a very simple example – say you want to use AI to createfizz buzz. We’ll do this twice – once with coding agents and another with Huzzah.
You start a chat in your tool of choice, and type something like the following:
Create a function that loops 100 times. If the number is divisible by 3, print “fizz”. If the number is divisible by 5, print “buzz”. If the number is divisible by both (like 15 for example), print “fizz buzz”.
If you need to make an edit, you’d send a follow up message to the chat:
Instead of looping 100 times, the function should take a number input and the function should loop that amount of times.