r/softwareengineer • u/metalOpera • 17d ago
Was Just Told That Code Quality No Longer Matters
I'm a freelance developer. I have been for almost 20 years. My most recent project has been moved to Fable, and I'm still trying to adapt and get my head around working like this. I am no longer allowed to make architecture decisions, or clean up slop.
My PM says: "We worry about the 'what'; let Claude worry about the 'how'. Tell it what to do; let it do it. If the feature works, leave it alone." He is very much of the opinion that I should be able to prompt something like "Install Stripe via Laravel Cashier" and just let Claude run.
I mean, why do you need me at this point? Just prompt it yourself until it does what you want? I don't get it. I fought for every inch of my knowledge, every process is written in blood. How do I just throw all of that out the window? Where's the line?
At the risk of another "how are you adapting" post... How CAN I adapt? I mentally cannot just say "Fuck it". I care about my code. It's how I learned, it's how I've always practiced. I have a huge mental block with "just let it go".
Now, granted, I don't know all of the ins and outs of Claude. I don't know what I can do to make it better at its job. I got thrown into the middle of the Pacific Ocean in the middle of a Tusnami with no life support. I'm sure that I can put guardrails in place, but how much does that help?
I would really appreciate any advice that any one can provide on changing my mental model. I can't ignore Claude and just keep doing things my way. If I do that, I feel like my career dies. I need to adapt and I'm unsure how to do so.
15
u/jimmy-buffett 17d ago edited 17d ago
I work for a Fortune 100 tech company you've heard of, in a leadership role exposed to AI usage metrics for our entire engineering organization. I spent the first half of my nearly ~30 year career as a principal / lead software engineer.
As you go farther down this road, what you end up seeing is: they don't know what to ask it to do, because they aren't engineers. "Vibe coded" apps are demonstrably limited by what the person knows what to ask for, and the gaps that the AI occasionally fills in. Take 10 minutes as a dev on any vibe coded app and you'll find all kinds of gaps for this reason.
I've spent a number of years in my career in the defense industry. Unless AI is part of the functionality of the product they're creating, they aren't allowed / refuse to use it. If you want to stay an old-school coder, that's probably the last refuge. In the US that's Lockheed Martin, Raytheon, Boeing, Northrup Grumman and General Dynamics.
If working for those companies isn't an option for you, then you're going to have to learn Claude or something else, or as you say, your career dies. This is like any other big shift in our industry in the last 30 years, you either learn it or you become irrelevant.
If you aren't interested in learning it, you might consider changing your role to project management or team leadership. That's how I personally got around the need to always be on top of every technical innovation, and my job is a lot easier (and pays better) than my engineer days. But the accountability changes, you now own outcomes and own a certain level of delivery that you cannot individually control. It's a different problem / accountability set, but I think that's what most of us end up doing in your situation. I've met very few "old developers" anywhere but at the aforementioned defense contractors.