domain experts can build with AI but can they ship? 🚢💨 not without the last mile. i'm onboarding folks who in their first week fire 30k lines out of a cannon before fully understanding what a PR is. what they can't do is the part that turns "it works on my machine" into "it lives in a codebase without busting the next person's vibes." merge conflicts. design system drift. security review. the test suite. the guardrails we set up for Claude's next battle. am i a code-review bot? a Claude whisperer? more like a reformed control freak helping a startup's internals survive five non-engineers shipping multiple times a day. whatever we call that now, it's the job.

i've been coding for about how long i've been a dad, 8 years. i've been using AI seriously for 8 months. some days i feel like i'm running circles around me a year ago. some days things get launched that i wouldn't have even swung on. other days i feel like i'm playing pretend, like the fire i've been given will burn out just as quick as it started. maybe. but whatever's happening is too new for anyone to actually feel like they belong, so just keep shipping until the doubt fades to noise. ✌️

rules people have to hold in their head rarely transfer to their hands. i want to go fast. i want my team to go fast. and i want to scale — not spend my productivity gains policing standards after the fact. so i flipped every type to strict. every lint rule to error. every function necessary and tested. in practice, three Claude agents (and me) cleared 320 violations in 10 minutes, validated in 20. the kind of "nice to have" that i never would have gotten around to. a dark factory should have neon guardrails.

rules people have to hold in their head rarely transfer to their hands. i want to go fast. i want my team to go fast. and i want to scale — not spend my productivity gains policing standards after the fact. so i flipped every type to strict. every lint rule to error. every function necessary and tested. in practice, three Claude agents (and me) cleared 320 violations in 10 minutes, validated in 20. the kind of "nice to have" that i never would have gotten around to. a dark factory should have neon guardrails.

everyone's looking for 10x productivity in the wrong seat. it's not your engineers. the pairing nobody's measuring: a domain expert — ops lead, finance analyst, growth marketer, founder — driving agents, and an engineer supervising the diff. process can't be an afterthought and documentation is key infrastructure. pair programming takes on a new meaning.

synaptic slop. 5x productive. 5x less fulfilled. i let claude do the things i used to do myself. the context window remembers what i was building. i don't. paid for the destination with the journey. not sure that math is mathing.