zlacker

I’ve been thinking about the SWE employment conundrum in a post-LLM world for a while now, and since my livelihood (and that of my loved ones’) depends on it, I’m obviously biased. Still, I would like to understand where my logic is flawed, if it is. (I.e I’m trying to argue in good faith here)

Isn’t software engineering a lot more than just writing code? And I mean like, A LOT more?

Informing product roadmaps, balancing tradeoffs, understanding relationships between teams, prioritizing between separate tasks, pushing back on tech debt, responding to incidents, it’s a feature and not a bug, …

I’m not saying LLMs will never be able to do this (who knows?), but I’m pretty sure SWEs won’t be the only role affected (or even the most affected) if it comes to this point.

Where am I wrong?

>>sirsto+(OP)
I think an analogy that is helpful is that of a woodworker. Automation just allowed them to do more things at in less time.

Power saws really reduced time, lathes even more so. Power drills changed drilling immensely, and even nail guns are used on roofing project s because manual is way too slow.

All the jobs still exist, but their tools are way more capable.

>>MR4D+n2
Automation allows one worker to do more things in less time, and allows an organization to have fewer workers doing those things. The result, it would seem, is more people out of work and those who do have work having reduced wages, while the owner class accrues all the benefits.

>>MR4D+n2
I think you’re making a mistake assuming AI is similar to past automation. Sure in the short term, it might be comparable but long term AI is the ultimate automation.

>>babysh+t4
We seem to be pretty good at inventing jobs both useful and pointless whenever this happens. We don't need armies of clarks to do basic word processing these days but somehow we still manage to find jobs for most people.

>>ImaCak+r5
Most of those jobs have terrible pay and conditions, though. Software engineers have experienced a couple of decades of exceptional pay that now seems to be in danger. An argument can be made that they are automating themselves out of a job.

>>MR4D+n2
This is how I use LLM’s to code. I am still architecting, and the code it writes I could write given enough time and care, but the speed with which I can try ideas and make changes fundamentally alters what I will even attempt. It is very much a table saw.

>>babysh+t4
We're in the jester economy - kids now want to grow up to be influencers on TikTok and not scientists or engineers. Unfortunately, AI is now able to generate those short video clips and voice overs and it's getting harder and harder to tell which is generated and which is an edited recording of actual humans. If influencer is no longer a job, what then is it going to be for kids to aspire to?

>>fragme+w9
Something useful, one can hope.

>>sirsto+(OP)
Software engineering (and most professions) also have something that LLMs can't have: an ability to genuinely feel bad. I think [1] it's hugely important and is an irreducible advantage that most engineering-adjacent people ignore for mostly cultural reasons.

[1]: https://dgroshev.com/blog/feel-bad/

>>babysh+t4
Table saws do not seem to have reduced the demand for good carpenters. Demand is driven by a larger business cycle and comes and goes with the overall housing market.

As best I can tell, LLMs don’t really reduce the demand for software engineers. It’s also driven by a larger business cycle and, outside of certain AI companies, we’re in a bit of a tech down cycle.

In almost every HN article about LLMs and programming there’s this tendency toward nihilism. Maybe this industry is doomed. Or maybe a lot of current software engineers just haven’t lived through a business down cycle until now.

I don’t know the answer but I know this: if your main value is slinging code, you should diversify your skill set. That was true 20 years ago, 10 years ago, and is still true today.

>>sirsto+(OP)
> Informing product roadmaps, balancing tradeoffs, understanding relationships between teams, prioritizing between separate tasks, pushing back on tech debt, responding to incidents, it’s a feature and not a bug, …

Ask yourself how many of these things still matter if you can tell an AI to tweak something and it can rewrite your entire codebase in a few minutes. Why would you have to prioritize, just tell the AI everything you have to change and it will do it all at once. Why would you have tech debt, that's something that accumulates because humans can only make changes on a limited scope at a mostly fixed rate. LLMs can already respond to feedback about bugs, features and incidents, and can even take advice on balancing tradeoffs.

Many of the things you describe are organizational principles designed to compensate for human limitations.

>>MR4D+n2
How many wood workers were there as a proportion of the population in the 1800s and now?

>>moregr+Jc
> Table saws do not seem to have reduced the demand for good carpenters. Demand is driven by a larger business cycle and comes and goes with the overall housing market.

They absolutely did. Moreover, they tanked the ability for good carpenters to do work because the market is flooded with cheap products which drives prices down. This has happened across multiple industries resulting in enshittification of products in general.

>>sirsto+(OP)
The way I see it:

* The world is increasingly ran on computers.

* Software/Computer Engineers are the only people who actually truly know how computers work.

Thus it seems to me highly unlikely that we won't have a job.

What that job entails I do not know. Programming like we do today might not be something that we spend a considerable amount of time doing in the future. Just like most people today don't spend much time handing punched-cards or replacing vacuum tubes. But there will still be other work to do, I don't doubt that.