less than a year ago, ai assisted around the edges. today, I work almost exclusively by chatting with models and reviewing agent diffs. when generation costs drop to zero, reading the diff becomes the whole job, human review becomes the sole bottleneck, and domain mastery remains the only way to spot subtle errors in code you did not write.
ai models generate code in seconds, but verifying that code takes real time. when you accept an ai edit without reading every line, you do not just risk subtle bugs like a union switched to a union all. you lose the memory of authoring the code, which leaves you stranded when something breaks.
in ai liberty i argued that capable models take more liberties and need robust guardrails, but i did not show them. this is the concrete kit i actually use to keep speed without losing control, namely read-only and ask modes, command allowlists, scoped database credentials, branch protection, and human-in-the-loop gates for the few actions that are genuinely hard to undo.
i now write once in my site workflow and let automation handle distribution to dev.to and linkedin, so each post reaches people consistently without manual copy and paste.
i share a real failure mode where an ai agent created and then deleted files while debugging, leaving a clean git tree but low confidence. the lesson for me is simple: ai should accelerate the work i own and understand, while domain-specific decisions stay with the people accountable for that domain.
the six ai models i keep in rotation in cursor, including composer, gpt-5 codex, claude, gemini, grok, and kimi, with what each is best at and when i reach for it
i connect my editor to jira and github through mcp, create well-structured issues from templates before coding, and reuse that text in pull requests so every agent in the chain has the same ground truth.
i have watched ai move from a prototype side assistant to an operational core system. this post shares that journey with time-stamped benchmark evidence and a practical view on where model usage is headed next.
this follow-up post gives practical, generic templates you can adapt for rules, skills, and commands, plus side-by-side examples that show why tighter structure improves ai execution quality.
this kickoff post explains why ai-authored rule, skill, and command scaffolds are often clearer for ai execution, and how to keep humans in control with constraints, reviews, and acceptance checks.