Dear tech executive, If you don’t know what you want or can’t articulate it coherently then speed isn’t your problem. Assuming AI code generation solves your problem is dead wrong.

“My engineering team consistently delivers the wrong thing.”

That’s a failure of definition, not implementation. Leadership either doesn’t understand the opportunity well enough to communicate it, or there isn’t one to begin with.

“Fail fast, learn cheap” works if you have something to learn from the experiments. If you can’t clearly articulate what you want, you won’t extract useful lessons from what gets built. Just building the wrong things faster isn’t the cure for that disease.

I vibe code unimportant things and test drive important ones. But I pushed the boundaries on some scripts to sync a client calendar where the calendar server is locked down to prevent our preferred and well tested sass solution.

Well. That backfired. It was consistently inconsistent on date ranges so a dedupe cycle of retrieve range with generic title from cal 1, delete, retrieve range from cal 2, add to cal 1 with generic title were two different ranges. Creating duplicates in the mismatched range.

Then in the attempt to fix that, I didn’t notice that it had removed the generic title part of the filter criteria and all my calendar events got deleted.

Not what I expected to occupy part of my day.

Welcome to the new era of going fast and breaking things.

Data is pretty clear. AI amplifies existing weaknesses as readily as existing strengths.