My sister used to be an engineer at Meta. she barely writes code from scratch anymore. literally a massive chunk of her implementation is just routed straight through Claude Code. typing out boilerplate or manually wiring up basic components is basically a thing of the past for her. seeing the constant existential dread in this sub lately (with all the daily posts about how Opus 5 or Fable is going to replace us), I asked her if she was worried. Surprisingly, she is one of the least anxious devs I know. we were talking about it over the weekend, and she basically broke down her day-to-day into five parts: Looking at broken telemetery, user feedback, or business metrics, and deciding what is actually worth building. Writing the proposal, arguing with PMs, and convincing leadership to allocate time and headcount. Designing system architecture, writing code, and pushing the PR. Waking up for a 3 AM incident call when something breaks, isolating the bug across conflicting services, and owning the fallout. Interviewing, mentoring juniors, and keeping the team from quitting. right now, Claude is mostly eating part three. its getting scary good at syntax production. And that footprint is expanding. You see it with Claude handling the syntax, and other tools like lovable,Enter Pro , v0 trying to automate the infra and deployment side. watching how these tools try to stitch together the rest of the pipeline, like connecting frontends to databases and deployment, makes me wonder how much of the broader implementation pipeline is actually going to be left for us to manually wire up. the implementation layer is getting compressed. But here is the uncomfortable truth that keeps her job safe: the tool cannot take responsibility for the outcome. even if tools like Claude Code write and deploy a setup in minutes, an AI still can’t tell a business which problem is actually worth solving. It can’t negotiate a technical tradeoff between two stubborn infra teams. most importantly, you can automate the work, but you cannot automate the accountability. the code might be written by Claude, but the PR still goes out under your name. When a badly prompted agent hallucinates an aggressive database migration, or a missing row-level security policy exposes user data, the company is not going to page Anthropic. they are going to page you. Management doesn’t care that the AI wrote it. You reviewed it, you merged it, you own the incident. The AI transition probably won’t make engineering irrelevant. It’s just making syntax production cheap enough that we can finally see which parts of engineering were never about typing code in the first place. Engineers whose entire career identity is built on translating explicit Jira tickets into syntax are exposed. But engineers who can deal with ambiguity, defend an architecture, audit AI output under pressure, and own the risk? they are about to become way more valuable. It does make me wonder, though. If Claude Code is handling the vast majority of the actual implementation work, are your tech leads actually measuring your performance now? are they still counting PRs, or has the evaluation metric shifted to something else? submitted by /u/Unpleasant-ex
Originally posted by u/Unpleasant-ex on r/ClaudeCode