We are not developers anymore, we are reviewers.

LLMs 621 points 149 comments 1 week ago

I’ve noticed a trend lately (both in myself and colleagues) where the passion for software development seems to be fading, and I think I’ve pinpointed why. We often say that LLMs are great because they handle the "boring stuff" while we focus on the big picture. But here is the problem: while the Architecture is still decided by the developer, the Implementation is now done by the AI. And I’m starting to realize that the implementation was actually the fun part. Here is my theory on why this is draining the joy out of the job: 1. Writing vs. Reviewing: coding used to be a creative act. You enter a "flow state," solving micro-problems and building something from nothing. Now, the workflow is: *Prompt -> Generate -> Read Code -> Fix Code.* We have effectively turned the job into an endless Code Review session. And let's be honest, code review has always been the most tedious part of the job. 2. The "Janitor" Effect: it feels like working with a Junior Developer who types at the speed of light but makes small but subtle, weird mistakes. Instead of being the Architect/Builder, I feel like the Janitor, constantly cleaning up after the AI. 3. Loss of the "Mental Map": when you write code line-by-line, you build a mental map of how everything connects. When an LLM vomits out 50 lines of boilerplate, you don't have that deep understanding. Debugging code you didn't write is cognitively much heavier and less rewarding than fixing your own logic. The third point is probably the one I dislike the most. Don't get me wrong, the productivity boost is undeniable. But I feel like we are trading "craftsmanship" for "speed." Is anyone else feeling this? Do you miss the actual *act* of coding, or are you happy to just be the "director" while the AI does the acting? TL;DR: LLMs take away the implementation phase, leaving us with just architecture and code review. Code review is boring.

More from r/ClaudeAI