Coding Required

Fuzzy In, Fuzzy Out

2026-05-112 min read

We caught ourselves doing something embarrassing with AI. Skimming the plan. Trusting the model. Hitting execute. Moving on.

It feels like speed. It's laziness wearing a costume.

The excuses come easy. We're busy. We're in a rush. There's too much on the list. "Let's just get the first version out and see." That last one is the trap. It sounds reasonable. It's how sloppy work ships.

Planning is the stage that matters. Execution is downstream. How we want to accomplish something can be a little fuzzy. What we want to accomplish must be laser focused. No model in the world turns a vague target into a precise outcome.

So this is the practice. We let AI draft the plan. Then we read it - actually read it. Five focused minutes, undivided attention, nothing else open. We try to spot flaws on purpose. Finding problems is the signal we're paying attention. We enrich it. Read it again. Enrich it once more. Then we execute.

It's boring as fuck. It's the only thing that works.

And there's one question at the end of all of it. The only one that matters.

Can we explain this plan to someone else - and will they understand?

That's the whole test. If yes, the what is clear. If no, we are not done.

Speed isn't the enemy. Laziness pretending to be speed is.


"If you cannot explain the plan, you do not have a plan."

Anbin Muniandy
CEO & Principal Engineer, YoPrint