Marshall Belles

Reviewing PRs was the first to go, honestly. (Almost) everyone hates reading the AI generated code that your fellow peers didn't even bother to read before submitting. What do we 'engineers' actually care about? If the job got done, it's debugged, you gave a $#!t to have the AI perform a basic red-first TDD, or at the bare minimum threw 'systematic debugging' into your prompt. If a quarter of the new code gets actual human attention I'd be shocked. Don't get me wrong, I always 'see' the new code, I don't 'read' into it like I used to, before this all came to be.

So what do we automate next? IMO: nothing. Having an engineer drive the AI conversation is cheaper and more effective - if it's not, train or prune your workforce and hire new guys who have the AI skills. Put a fire under their A$$es. I've setup several automated 'developer' pipelines and workflows - none of them beat me plus a few Claude Max plans. As the models get better, so do we. Keep building these skills guys, if you're not alredy writing engineering loops - look into using /loop and workflows.

✌️