I'll be honest — I'm still figuring this out.
After 10 years of building software, I've started letting AI write a lot of our code.
It's fast. Sometimes humbling. Often better than I expected.
But building billing software for water and utility companies taught me something early:
a "small bug" here can mean a wrong bill in thousands of homes.
So before we went further, I sat down and wrote a short list —
the decisions I'm choosing not to hand over to AI.
Not because AI isn't capable.
Because someone has to be accountable when it matters.
My list so far:
1. Approving a production release
2. Signing off billing truth — tariffs, rules, test cases
3. Waiving a critical billing or data-isolation failure
4. Changing the AI's own rules, scope or budget
5. Authorising security or penetration testing
6. Telling customers when something goes wrong
Vibe coding hasn't made the hard part disappear.
It's just moved it — from "how do I write this?"
to "what must never go wrong?"
It's a work in progress, and I'd genuinely like to learn from yours.
What would you never delegate to AI?
#VibeCoding #AIinEngineering #UtilityTech #BuildingInPublic
Originally posted on LinkedIn. Join the discussion there ↗