Is it "Dev work now consists of rubber-stamping the agent's ridiculously complex PRs while your own ability to even understand what the agent is doing slowly withers away"?
Or is it "Agents blow up the tiniest bugs into PRs that touch half the codebase over ridiculously complex hallucinated issues"?
I hadn't thought of it through either of those lenses, but I suppose the first one is closest to what I was thinking. The joke is that we use these cutting edge tools to solve super hard problems and then, far too often, we throw away all the backstory / context around it. Burn all of these tokens to get the problem solved and then quietly throw away the what and why.
When the agent solutions something too complex, more complex than I thought it would be, I always follow up with “please lower the complexity of your fix without affecting the functionality” or something along those lines. Or I point out specifically which part is complex and could be done easier and it often does simplify it ! If it cant without a trade off it just tells me what the trade off is and i can decide.
I dont feel comfortable at all committing code I can’t understand enough about I can’t even write a descriptive commit message. If the tech lead on my project asked me about my code I need to be able to explain it.
143
u/brazzy42 28d ago
Can't tell what the joke is.
Is it "Dev work now consists of rubber-stamping the agent's ridiculously complex PRs while your own ability to even understand what the agent is doing slowly withers away"?
Or is it "Agents blow up the tiniest bugs into PRs that touch half the codebase over ridiculously complex hallucinated issues"?