Comment by simonw
1 day ago
The more time I spend accelerating my work with AI tools the more I realize how incredibly hard the craft of shipping useful software actually is.
Sure, Claude Code and Codex can write (most of) the code for me - but the amount of technical knowledge I need to decide what and how to build remains enormous.
As an example: I'm working on a system right now that works like Claude Artifacts, allowing custom HTML+JS apps to safely run in an iframe sandbox inside a larger application.
Just understanding why that's a useful thing that can be built requires deep knowledge of sandboxing, security threats, browser security models, and half a dozen different platform features that have been evolving over a couple of decades.
A vibe coded without that technical understanding would have zero chance of prompting such a thing into existence, no matter how much guidance the LLMs gave them.
It really saddens me to see some developers talk about literally quitting their careers over AI, right when the benefits of existing deep technical experience have never been more valuable.
> It really saddens me to see some developers talk about literally quitting their careers over AI, right when the benefits of existing deep technical experience have never been more valuable.
1. Because the experience of interacting with AI is miserable. I like writing code. I don't like finding the magic incantation that gets the machine to write the correct code. I don't like correcting the machine when it gets things wrong. I don't like any of this, it's awful and I would never have gone into this field if someone had told me that it would be like this one day.
2. I cannot condone the means by which these tools were created, which is, as far as I am concerned, theft. I think it's unethical to use them at all, because they were created unethically. I dislike using stolen work, I think it's wrong, and I think everyone who uses it is making the world worse and normalizing theft. If continuing in my career means that I have to compromise my ethics, I wouldn't do it even if I loved this stuff, and see point (1).
3. Is anyone going to pay me more for my "more valuable" skills? Doesn't seem like it, engineering salaries on the whole are going down right now. You can believe they'll go up eventually if you like, but there's no evidence that will happen, or that it's happening. If my employer captures all the value, why should I care whether I'm creating more of it?
> Because the experience of interacting with AI is miserable. I like writing code.
I'm your exact opposite.
I've felt like code is 1960's punch card tech my entire career. I've always wanted to do more.
So much of coding is plumbing. Or paying attention to tiny little details. Or hunting down stupid bugs. Or changing requirements and refactoring. That shit sucks. All of it.
I've never had so much fun with software. It's starting to feel like magic. And because we possess deep understanding, we are uniquely positioned to take advantage of this.
The AST is not the objective. The finished product is. Our DNA is by all accounts filled with garbage. Let your feelings about code purity and sanctity go. It's the job to be done that matters.
Code is not holy. In 100 years people will look at our ephemeral artifacts as silly little things. Treat it that way today. Means to an end.
"the sand doesn't matter, only the beach does"? Makes no sense.
Perfection is achieved when there is nothing left to take away.
> In 100 years people will look at our ephemeral artifacts as silly little things
Whereas they'll totally admire the hamster wheels in which people shoveled product? Well, I don't care either way. Craftsmanship and care have their own rewards, and shape the person engaging in them for the better.
4 replies →
>Or paying attention to tiny little details
That's like, the entire point and the entire reason any of it works with any sense of reliability. Did they not do the "tell me how to make a sandwich" gag to show why thinking about the details matters? Ignoring them is how you end up with borderline unusable applications slower than they were with 10 fewer years of hardware development. I guess I shouldn't be surprised.
> So much of coding is plumbing. Or paying attention to tiny little details. Or hunting down stupid bugs. Or changing requirements and refactoring. That shit sucks. All of it.
No offense, but this sounds like you just don't like anything about writing code and you don't have any LLM superpowers, because those are the technical skills that make you good at being a software engineer regardless of whether you're using an agent.
> Code is not holy. In 100 years people will look at our ephemeral artifacts as silly little things. Treat it that way today. Means to an end.
I don't give a shit about code as an artifact. Writing code to solve problems is fun. Prompting an AI to solve problems makes me want to eat a gun. That's a real difference and it's not something I can just change about myself.
1 reply →
I mean, if you don’t like refactoring, which is my absolute favorite, it’s hard to believe you understand software engineering and software architecture.
Tedium absolutely exists in coding. And is usually a sign of bad interfaces and/or architecture.
For most of us it wasn’t really about getting the user to do X. It’s getting the user to do X at 1/10th of the price, 10x the speed, and the user is left absolutely amazed.
Magic is for the user to experience. Not for the user of the programming language.
1 reply →
This is a refreshing opinion, and also matches with my own experience. Many software engineers around me have now made the conclusion that AI will take their jobs and they're thinking changing careers already. I feel this is too early to tell. The prompts I write are all very technical, someone without my expertise would struggle with just an agent to talk to. Every time I do something outside my expertise, it is not as fast as one would imagine. Expertise do help tremendously and keep things in order
in fact engineering job openings are skyrocketing, just far beyond the big megacorps. AI was a neat excuse to correct the covid overgiring phases, now axes happened while lots of people built lots of new things they couldn't before and at some point it "swamps" under the complexities of reality at scaling up, thus engineers are needed. jibs are shuffling around yes, but demand will be surging even more soon.
> It really saddens me to see some developers talk about literally quitting their careers over AI, right when the benefits of existing deep technical experience have never been more valuable.
But that's not what senior executives think. That's all that matters. If they think that AI can replace engineers, so let it be. I mean, since when senior executives know shit about what quality means? They only care about revenue and profit. So yeah, you're right, but that's not gonna happen (sadly)
That’s very black and white. An org with a sizable enough engineer employment base will have leaders who understand that engineering is a deep discipline and quality matters, after all what they sell is an SLA. Sure not all orgs are like that, but AI has not changed the calculus: fast / cheap / good, are tradeoffs long discussed before AI.
I can’t just quit the “career” that I’ve spent years building (for what else?). I’ll just fade somewhat gradually into unemployment, I imagine.
> can’t just quit the “career” that I’ve spent years building
One, I think the talk about AI replacing developers is tripe. We’re still correcting the post-Covid hiring binge.
Two, even if that level is breached, I’d consider your skillset more broadly than what you can literally do right now. Organizing people and technical systems is hard. And the article highlights how that doesn’t seem to be something AI is focused on improving on right now. (Would take larger context windows. Which would make inference more expensive.)
I firmly believe that your existing skills and experience are more valuable in a world where the AI tools can speed up the bit where you type the code.
It's great that you believe this, but are you hiring?
I don't intend this to read as pure snark, but someone's abstract value isn't much good to them if the job market itself can't / won't recognize it.
2 replies →
“ the more I realize how incredibly hard the craft of shipping useful software actually”.
I posted something here not long ago re. There is a huge amount of craftsmanship in between a great idea and great product. And it received a lot of downvotes.
LLM’s don’t change this in reality. That’s why we haven’t seen an explosion of high value products. Creating a product in the first place that create value is VERY, VERY HARD! The arrogance of people to dismiss it because of the existence llm’s is hilarious.
Right!
And it's not just the product design either - the number of steps it takes to get a piece of software in front of other people, correctly deployed, with backups and analytics and monitoring and a domain name...
Even with all the LLM help in the world you still need to know a whole lot about how web software works to pull that off.