How I Use AI

A mentor of mine has a name for something I feel constantly: working with AI mostly feels solo, and calling it a "team" flattens something real. That framing is his, not mine. He also has a name for the other half of it, the 75% trap: the 75% keeps getting easier, and the 25% is where the work lives. My own projects taught me the same thing: AI gets you to a rough, working draft fast. Embarrassingly fast. Getting from that draft to something you'd put your name on is still the job, and that part is still mine.

I test this against my own work. This site went through a written plan, then every task got implemented, then reviewed twice (once for whether it matched the spec, once for whether the code itself held up) before I'd call it done. That second pass caught real bugs: a slider that snapped where it shouldn't, images that would've gone permanently invisible if a script failed to load. Nobody catches those by trusting the first draft.

Agile Defense works the same way. We build concept prototypes fast, sometimes in days, because the fastest way to find out if an idea holds up is to put it in front of someone who knows the problem firsthand. AI gets the prototype into someone's hands quickly. My job (and my team's) is reviewing what comes out before it goes anywhere near a client, same judgment, just applied earlier.