Hacker News new | past | comments | ask | show | jobs | submit
I came close to thinking that way a couple years ago, but I've become more optimistic. There is no shortage of problems that can be solved (in fact, wants are infinite), and LLMs may actually enable our profession to reliably deliver them better than 50% completion.

I've also seen non-technical folks in the corporate and government worlds glom onto vibe coding, only to start flailing like they were caught in a rip current when the underlying technical debt is too strong, even with strong and capable models.

For a certain type of engineer who enjoys really arcane technical problems, yeah, the gravy train may be over, or at least will involve a lot more machines than it used to, as Alan Turing predicted about "mechanical work" becoming a "drudge."[0]

And I think Big Tech is for the foreseeable future a sink for capital in the form of specialized hardware rather than human capital.

[0]https://en.wikiquote.org/wiki/Alan_Turing#Quotes

The arcane technical problems aspect of the job has always been changing; LLMs are just a continuation of the trend.

I'm old enough to remember when compiled languages like C were bemoaned by people because their skill at crafting assembly by hand was suddenly less important. Or similarly with people who were brilliant with arithmetic, or symbolic manipulation, or manual drafting/lettering. These skills were all paramount at one time, and it's natural that the people who excelled at them will feel a sense of loss.

The real goal, however, will always be to solve real-world problems. Engineering consists of whatever gets you there most effectively.

Bullish on AI in the long to medium term but that doesn’t change the fact that it’s displacing junior level jobs now.

Several students I have been trying to help enter the field are facing greater barriers than I have ever seen. Not just leetcode but dozens of interviewing rounds. The problems that they are asked also feel increasingly hard and it seems like interviewers are using AI during the interview while forbidding the interviewee from leveraging any external aids.

We are really burning the next class of developers with the current interview process

> Not just leetcode but dozens of interviewing rounds.

I cannot believe that companies are still using leetcode. That's just complete idiocy. The game is all about reading and understanding code now. Anyone who is still conducting timed code trivia examinations has completely lost the plot.

Stop cargo-culting your interview process, and use your brains!

loading story #50569778
loading story #50573659
loading story #50571224
loading story #50569658
loading story #50570059
loading story #50572240
loading story #50572371
loading story #50569740
loading story #50569828
loading story #50569965
loading story #50569520
loading story #50570485
loading story #50570490
expectations for juniors will change over time, ands university curricula for software engineering degrees with it
loading story #50568478
Going from asm to C is a different mode of thinking, but a cerebral challenge nonetheless. The transition we're in includes a substantial disengagement of thought. For those of us who like thinking, this is something to mourn.
If you're ambitious enough, there is still plenty to think about. Design, tradeoffs, what to measure, how to express your goals, what you value and want to spend more time going deep on, what counts as good enough, etc. A lot of decisions but they are of the sort where you also need to be given enough agency and decision by your company. The type of job where you're given a spec and you just code it up is indeed going away.

Maybe at some point AI will do this better too, and at some point they will just mind read you as to what you're trying to build so you don't even have to be able to verbalize it any more, but we are far from thatm

AI makes it possible to disengage from thinking, much more than past technologies did. You can prompt it with "yes, keep going" and just accept whatever it spits out. However, you'll still get better results if you are also thinking, and challenging it when it makes bad assumptions.

If you like thinking, you can keep thinking. AI can't stop you from doing that unless you let it.

I feel that some, I’ve also been able to take on just a huge scope of work and deliver satisfactory results, which is interesting in its own way.

Been able to finally remove a really painful and bad ORM from a legacy codebase.

> The transition we're in includes a substantial disengagement of thought

Not really, the problem is just changing. Just like C allowed developers to leverage a standard library and a checked type system to create software, AI is allowing developers to leverage english and verifiable specifications to create software. We're all still developing software per a set of requirements at the end of the day.

The varied implementations will always exist and the job is both picking the right requirements to work on, and delivering in a way consistent with its goals.

Really? I find the thinking is very different but I'm still keeping very busy. It's like never-ending PR review cycles.
Do you mind helping me understand a couple of things about your perspective?

> The transition we're in includes a substantial disengagement of thought.

While I think you are more correct than not, a cheeky part of me cannot help but think that humanity might be better served if some thoughts were never engaged with in the first place.

1.) I apologize if this is a rather blunt question, but how much of your identity is based on your own perceived (and perhaps exemplified/actualized) intelligence?

   I have had a fortunate enough life to have befriended many people who I consider to be far more intelligent than myself. Of these many individuals that I remain in contact with, I have noticed the ones that are the most adamantly opposed to the LLM frenzy, the "death of thought", etc. are the ones that have the strongest attachment/most pride in their own intelligence. I suppose it is a rational reaction, but I think LLMs are hurting a lot of people's egos. 
> For those of us who like thinking, this is something to mourn.

2.) That statement is what I am most curious about. Do you mind elaborating on what thought there is to mourn? What exactly is being taken away from you? I hope I am not about to come off as condescending, but what is actually preventing you from engaging in deep thought? One is not compelled to use AI outside of their own volition. Even in instances of employer mandates, one is not forced to use AI outside of their occupation.

loading story #50570404
disclaimer: Not the OP.

1. I feel like I have a decent amount of my identity tied up in being "smart". I have always enjoyed learning, have been good at solving problems, and have been able to get out of some pretty difficult circumstances that were definitely slanted against me in terms of being able to find a stable and high paying job through a combination of luck, being born decently smart, and hard work.

2. For my entire life I have been able to work towards or have a job where my purpose is to solve interesting problems and get paid well for it. I have been lucky enough to be in a position where I could paid to sit down and build solutions, understanding every intricate detail of what I made. And now, it seems like the entire industry is just throwing this away. Why engage with deep thought when everyone around is thoroughly convinced that the act of thinking is "last gen" or "going out of style"? If everyone else is wrong, that doesn't change the pressure to just stop thinking and ship 50 commits a day of unread slop. If everyone else is right, why bother thinking? I am just going to lose my job and be stuck doing menial labor until the AGI builds robots that can do my job. Either way I am unhappy. And sure, I do not need to use AI outside of work, but that does not change the existential dread of having the next 30-40 years of my career turned into something that I absolutely hate.

Overall, we have effectively built a machine or a widespread perception of a machine that rewards not thinking and not taking responsibility. Why bother trying to accomplish anything if a machine can do it better than you. I value solving problems, I value understanding, and I value working hard, and at least for me I feel that I may have to start mourning the fact that you used to be able to get paid to do all three. On the bright side, if anyone my age is poised to, by the stupid credentialism of our society, stay in the job market after this, it is me. So either I make a decent amount of money and escape the permanent underclass or all of society is cooked, in which case at least I won't be judged.

I spent years of my early career being the guy who could make websites look bubbly with custom border graphics stuffed into <table> layouts.

border-radius could have knocked me out of the game, but I decided to keep going. And I'm glad I did.

OMG wonder how many of us remember/experienced those times.. still remember using Java applets to do some interactive stuff and replaced that with Ajax when it was a thing! You are a hero web dev if you write 100 lines of Javascript.
I remember how frustrating it felt that website standards no longer mandated tables for layouts and we had to learn div layers. Not to mention the semantic web or the switch of dynamic content away from flash…

I’m excited about what this next progression entails. I’m building complex software in months in a home lab that would have required millions in investment just five years ago. In five years I don’t think any of us can say for certain what the industry will look like.

loading story #50568814
loading story #50568883
I love this comment.

SWEs who oppose AI seem to forget that they are paid to solve problems, not write code.

loading story #50568398
loading story #50567985
loading story #50567384
loading story #50566648
loading story #50567852
loading story #50566837
loading story #50566553
loading story #50568128
loading story #50567036
loading story #50568161
loading story #50570509
loading story #50567759
loading story #50566959
loading story #50568879
loading story #50568500
loading story #50567046
loading story #50570522
born just in time to watch the singular thing i enjoy in life get automated away. I guess i get to be like every other person now and hate my job.
If you only liked the “writing code” part of software engineer, then maybe software engineering just isn’t the right thing for you. Luckily now is also the best time ever to explore alternative career paths! One of the amazing things about AI is how it’s lowering the barrier of entry into new fields.

FWIW I love not having to spend so much time writing code. I get to focus on solving problems for end users, which is way more fun and rewarding IMO.

I enjoyed getting to solve problems elegantly and I still believe, even if it is old fashioned, that writing and understanding good code is essential to building the abstractions for and design of a good product. Except for maybe things like webdev, where looks good ~= is good, I feel like humans writing code is still the best way to do things, but I feel like I am in a growing minority and might just need to drop the field and become a welder or whatever.

It wasn't so much coding that I loved, although I do love that, but being able to build and understand something far greater than myself, and the puzzle of trying to find the right abstractions and tools to make something beautiful.

loading story #50570511
>singular thing i enjoy in life

If coding was it, you have a more serious problem than AI

loading story #50571491
What can I say, I liked my job.

(I'm excluding trivial, hedonistic things from what I enjoy)

> The real goal, however, will always be to solve real-world problems. Engineering consists of whatever gets you there most effectively.

Love this statement, 100% agree.

me also remembers when c++ was thought slow, so we were doing a mixture of C and assembly. it took my friends years to agree to java, then it took him 15 more to understand JS works better for him. happily it took him only 2 years (of convincing) that he should try LLMs and he's not so stubborn anymore :D
...and safely. Engineering has strong and rightful tradition in safety. Perhaps it is many times not as crucial as in the medical profession, but it is very important for engineers to understand and be able to mitigate risks that are associated with whatever they are building. You don't want your bridges to collapse or planes to fall out of the sky afterall.
loading story #50571634
>I'm old enough to remember . . .

yep

Every higher level brought worse craftsmanship but more products. Nobody programs like Mel, they don't need to make Blackjack run on 2k drum memory but the same lack of mindset makes PC video games 300GB big.

They're still relevant sometimes. ffmpeg core encode/decode routines are written in multiple different assembly languages. These very same LLMs run on highly optimized code on purpose-designed hardware (!) with plenty of symbolic manipulation to find the optimal execution routines.

3/5

I'm old enough to call you on your bullshit.

The best you can find is people claiming that it would reduce the amount of assembly people write, which was true. They also predicted programmers would lose their low level understanding of the machine. That was also true. They didn't predict anything about making human thought non-viable economically. And not one C compiler vendor said their product could cause human extinction.

If AI predictions have the same level of truth as C compiler predictions, then the doomers are right.

So what, specifically, are you calling them on?
I can't speak for them, however:

   compiled languages like C were bemoaned by people because their skill at crafting assembly by hand was suddenly less important. 
doesn't ring a bell from the time I went through that transition; people used C and FORTRAN and happily dropped back into handcrafted assembler as needed, and applauded the fully assembler works of some, etc - but nobody (in my recollection, was seriously bemoaning compilers and calling for a return to 100% assembler).

   similarly with people who were brilliant with arithmetic, or symbolic manipulation, or manual drafting/lettering. 
My mother was a computer, she didn't pine for the days of rows of meat computers; I took drafting as part of engineering and worked to assist and eventually replace drafting rooms for cartography- that was a slow rotation out and perhaps had the greatest impact of all the things listed- but people weren't exactly clawing to have their ink stain jobs back.

Symbolic manipulation is an interesting one - I recall a general distrust of Monster Group proofs so large they involved software generation and checkers ... but things are still advancing through that same distrust with lean and so on. What I did see is "symbol manipulators" diving into creating automated symbolic algebra suites such as Cayley (now Magma) and still using them today to crack Quantum encryption candidates, etc.

ie. It comes over a bit hyperbolic

The points of significant difference between Ye Olde Days and now is the numbers (absolute and proportional) of people affected, the speed with which they are affected, and the availability of related and meaningful work into which they can transition.

AI does not help stopping wars, ending poverty, solving climate wars.
I feel the same way. The discussion on commoditising programming skills has been going on since before I left school and what we saw was demand, and pay, skyrocket as accessibility of the profession increased. I believe it’s possible that making it more accessible makes problems that were uneconomical to even explore quite challenging but achievable.
loading story #50565376
loading story #50566094
IMO a decent developer can pick up most other roles, especially non-people-manager roles (though some pick those up very fast, too) a hell of a lot faster and better than most people in other roles can pick up programming.

Part of this, I think, is because the people who had the inclination and ability to pick up programing have, for decades, been nudged into programming from whatever job they had before, by comp, co-workers, managers, and opportunity availability, so they’re already heavily concentrated in programming even if they’re perfectly capable of doing other jobs (perhaps with some brief re-training).

I think other roles need to fear programmers who studied a new role for a couple weekends more than programmers need to fear LLMs. If we’re bumped out of full-time programming… guess where we’re going, and what we’ll be way better at doing than them?

[edit] part of that I wrote unclearly: the main thing about people being siphoned out of other roles into programming for the last 3ish decades is that most of the people with the combo of willingness and ability to get decent at programming… are programmers. It’ll tend to be harder to train other people to be good enough at using their computers to maximally benefit from LLMs (they already usually aren’t very good at using their non-LLM computer tools, it’s not like this is a new problem) than to shift programmers into other roles, if programming as a dedicated job in-fact is diminished in a durable way and at a mass scale.

I've had similar thoughts. I feel like with the context engineering skills I've built, I could theoretically go to quite a few types of white collar jobs (non-sales/people skills type jobs) and shadow their experts and slowly build up their workflows and heuristics in a job specific context harness. And then I could train myself to do their jobs.

But once people catch on to this dynamic, I doubt people are going to be helpful in these onboarding the AI guy jobs... It's a reaping, boil down the heuristics they spent a career building into a document tree, then push them out.

Most firms are in a very risk-averse mood as far as hiring. They don't want to take on the liability associated with this sort of workforce development stuff, and don't want to train and onboard people they might not need in a few years. At least not in the current monetary environment (which isn't going anywhere any time soon)
I agree. The transition will be messy though.
The issue is, there are going to be less and less people willing to give you money that you can make a living to address those infinite wants
loading story #50564763
loading story #50564812
loading story #50565157
loading story #50568900
loading story #50564771
loading story #50565294
loading story #50567861
loading story #50564777
loading story #50564765
This seems relevant! Wow, this is 1951.

> Let us now assume, for the sake of argument, that these machines are a genuine possibility, and look at the consequences of constructing them. To do so would of course meet with great opposition, unless we have advanced greatly in religious toleration from the days of Galileo. There would be great opposition from the intellectuals who were afraid of being put out of a job. It is probable though that the intellectuals would be mistaken about this. There would be plenty to do, trying to understand what the machines were trying to say, i.e. in trying to keep one’s intelligence up to the standard set by the machines, for it seems probable that once the machine thinking method had started, it would not take long to outstrip our feeble powers. There would be no question of the machines dying, and they would be able to converse with each other to sharpen their wits. At some stage therefore we should have to expect the machines to take control, in the way that is mentioned in Samuel Butler’s “Erewhon”. "Intelligent Machinery, A Heretical Theory" (1951), from a BBC radio discussion programme, The ’51 Society.

loading story #50570039
I hold the same optimistic view, rooted in Jevon's Paradox. However, it's not a law of nature, it still requires demand elasticity. That is what makes me more nervous, as what is playing out now in both the US and EU is a shift from monetary to fiscal dominance, with significant disruption of white collar occupations that has been predicted even within a world without modern generative AI.

So the question is if demand for software will expand by more than the productivity improvement it creates, in this fiscal environment. I think it will, but it will be for Software as a (Specific) Solution rather than the classic Software as a Service (delivering measurable outcomes vs. delivering tools for people to use), and this will come with a shift in the types of roles hired for. Less "routine" software developers, more people in product design, more domain specialists, more system architects and integration engineers, QA, security, compliance & auditing, etc...

Just anecdotally: I am finishing up on a project proposal for a company that would pre-AI probably never considered this, but if it's greenlighted, I will need a team in two months and I'm already nervous that I may not find the right selection of people... Many such initiatives are started now because AI makes everyone more ambitious, wanting to automate everything but reliably, which requires skilled software engineers in conjunction with AI workflows.

Yeah, it seems to me that nobody is better positioned to use these tools effectively than people who have already been building software "by hand". I still have some concern that we might hit a point where there is no human in the loop at all. But I don't feel very threatened by non-technical people vibe coding me out of a job.
loading story #50567654
Yeah I don't think the gravy train is gone for software engineers; it's just starting.

I feel very negatively about the rise of AI for many reasons, but personal economic prospects is not one of those reasons.

loading story #50572854
> There is no shortage of problems that can be solved

there is shortage. You can just jump on problem you want to solve, because distribution channels are saturated/occupied.

There is not infinite demand for software. And certainly not infinite demand for software that costs money. In my opinion we are hurtling towards a world where, outside of the huge tech monopolies, nobody invests in or pays for new software because making new software (even using AI) takes work and skill , but copying existing software takes relatively no work and no skill.

So someone invests time and energy into figuring out good UX, sensible architecture, and releases a good product. Then a swarm of clones come about and depreciate the value nearly instantly. Who wants to invest in making good products?

If you’ve used AI extensively you realize how easy it is to copy relative to create.

loading story #50569542
> I've also seen non-technical folks in the corporate and government worlds glom onto vibe coding

One of the biggest uses of vibe-coding that I've seen is non-technical users creating throw-away tools to help them solve their current problem.

I am more than convinced that the folks who understand how LLMs work, what they are good at and what their limitation are would make it out on top. Anyone who is still hands on would do just fine.

Within couple years there is definitely going to be a shortage of people who understand how systems work. The only black swan possibility is the enterprise industry getting too small cause of heavy consolidation.

within a couple of years I expect LLMs to understand how systems work well enough, and to be autonomous enough, that deep understanding of systems becomes largely irrelevant. right now LLMs can't manage the technical debt they create, but that's a problem that can and will be RL'd away. it probably hasn't already purely because the trajectories to sample are uneconomical to generate.

of course, I'll still be doing systems. maybe from my cabin in the woods, hiding from the machines, but I'm in it for the love of the game.

loading story #50568599
Systems might become even more opaque and morph in the next few years as AI models begin to make their own stacks for solution designs. I for one would welcome simplifying the overly complex stacks upon stacks of abstractions we have today. Instead, move back to having well-formed, proved unikernel blobs of execution (e.g. Symbolics). The sky is the limit.
Can be solved and must be solved are not the same thing

Are you solving a shared agreed upon real problem or just doing leetcode on arbitrary meaningless data structure?

There will still be jobs but orders of magnitude fewer jobs.

Closer to reality that existed before the 08 crash and ZIRP fueled ponzi schemes fueled the web SaaS mania.

US doesn't need 4+ million software devs

World doesn't need 50+ million software devs

...when big tech is just shipping black boxes that boot models to handle local inference

It just needs enough jobs to solve that big tech production pipeline

> I've also seen non-technical folks in the corporate and government worlds glom onto vibe coding, only to start flailing like they were caught in a rip current when the underlying technical debt is too strong, even with strong and capable models.

just happened on a client call yesterday. our work had been postponed because a new system was being introduced. our routine calls kept being cancelled and we started to worry. the customer finally showed up after a few months and told us the new system was demoed and "was clearly vibe coded. everything went wrong. they were asking claude questions during the demo" so were back in contract again

> reliably deliver them better than 50% completion

everyone has ideas. being able to program helped separate ideas from execution and i thought llms would remove that barrier but there seems to be some ingrained half-ass mentality in the self-proclaimed "idea guy"s ive met which prevent them from finishing things

loading story #50574058
> I've also seen non-technical folks in the corporate and government worlds glom onto vibe coding, only to start flailing like they were caught in a rip current when the underlying technical debt is too strong

Anecdata I’ve seen this too a few times. Major issues where a significant number of engineers had to stop important product work to un-jankify something a non technical person created. In every case those product people felt the heat so bad they basically stopped.

The funny thing is, people have been saying the same thing about programming for years.

In the 80's, when I was about to start a computer science degree, a friend said his father thought it was a dead end because the computer would be able to program itself soon. This was the era when 4GLs were beginning to be a thing.

So much of the job is just helping the business people figure out what they want and trying to regularise their ridiculous arcane manual processes.

loading story #50569462
Its pretty clear that software services companies will need to pivot to offer "slop fix" services. We offer Great Deals to Maintain AI Generated Software! Clean up your Code! Delete your Technical Debt! Cheap Contracts!
You joke but this is actually good idea.

“Is your vibe coded ATC system grounding flights nationwide?”…

On the one hand, the models are definitely not good enough to replace human coders in all areas. I get great results from them, but they need some back and forth to get there. I'm in no danger of being replaced right now.

On the other hand, just two years ago they were practically useless for anything non-trivial. In that time, they went from "might be cool someday" to "can do most of the work, but still needs handholding." What are they going to look like two years from now? Five years? Ten?

So much depends on where we are on the S-curve. If we're getting into diminishing returns, then we may top out at a point that isn't too far beyond what we have today, where they're highly capable but need that human judgment and oversight. If we're at the bottom of the curve, it's hard to know what the future would look like. I have no idea which one is closer to being true, and I don't think anyone else does either.

loading story #50565053
I strongly disagree with your optimism about the extent to which our profession will continue to exist --much less offer the best effort/reward ratio for the top ~10% performers of any major profession by far-- but I do love and appreciate you for quoting Mr. Turing. I have an another, far more relevant quote to offer in response though, from an under-appreciated essay:

  Let us now assume, for the sake of argument, that these machines are a genuine possibility, and look at the consequences of constructing them.
  To do so would of course meet with great opposition, unless we have advanced greatly in religious toleration from the days of Galileo.
  
  There would be great opposition from the intellectuals who were afraid of being put out of a job.
  
  It is probable though that the intellectuals would be mistaken about this.
  There would be plenty to do in trying, say, to keep one's intelligence up to the standard set by the machines, for it seems probable that once the machine thinking method had started, it would not take long to outstrip our feeble powers.
  There would be no question of the machines dying, and they would be able to converse with each other to sharpen their wits.
  
  At some stage therefore we should have to expect the machines to take control, in the way that is mentioned in Samuel Butler's *Erewhon*.
In case it's not obvious: things do not work out in Erewhon :(
You have not had to seek a new job in this market. I’ve had 2 interviews in 4 months. Where is my LLM optimism for niche problems that will save me?
loading story #50566785
An example to counterbalance this is art. Art had a market of people willing to pay for it - some private, some companies - art including graphic design etc.

But the thing is that with AI the number of people willing to pay you to solve their art problem has dramatically fallen. The total number of jobs in art in general has plummeted. The opportunities to make a living or develop yourself with art have similarly plunged.

So there will always be another problem but that doesn't mean there will always be someone willing to pay you to solve it if they can get by without you.

"You can train an LLM on all the notes in classical music up to the 18th century -- but will it ever invent jazz?"
loading story #50567379
loading story #50566235
loading story #50567491
loading story #50565539
> There is no shortage of problems that can be solved (in fact, wants are infinite), and LLMs may actually enable our profession to reliably deliver them better than 50% completion.

Seems like copium to me if we're being honest.

Why would anyone pay you to solve the problem when they can just throw it at a cheap LLM?

And if the answer is that you have some sort of special taste or domain knowledge, once your solution is out in the world how are you going to stop someone from using an LLM to copy it and then undercut you in an immediate race to the bottom for everything?

loading story #50565186
loading story #50564922
loading story #50564976
loading story #50564851
loading story #50564878
loading story #50565139
I have been in software development for over 30 years and when people mention AI taking over jobs, I keep coming back to the demand problem. Where will the money come from to pay for anything if no one has a job?
loading story #50565666
loading story #50565618
loading story #50566041
loading story #50569678
loading story #50571808
loading story #50568192
loading story #50565555
loading story #50565420
What do you mean "a couple years ago"? Opus 4.5 isn't a year old yet. I don't necessarily disagree with your take, but starting off by saying you updated your view two years ago seems... outdated?