Hacker News new | past | comments | ask | show | jobs | submit
Genuinely a massive moment in human history. I'm nervous about what comes. as a SWE the gravy train is basically over in my view. they figured out how to make a program that does the job. Always thought i was set for life. difficult to grasp how much life will change in the coming years.
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.

loading story #50568119
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.
loading story #50569222
loading story #50569076
loading story #50570004
loading story #50570218
loading story #50568612
loading story #50569855
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.

loading story #50568457
loading story #50568575
loading story #50566287
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.
loading story #50570401
loading story #50570358
> 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.

loading story #50568726
loading story #50571179
loading story #50570189
loading story #50569065
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?
loading story #50568440
loading story #50566921
loading story #50565225
loading story #50564704
loading story #50569982
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.

loading story #50569914
loading story #50566438
loading story #50566758
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.

loading story #50566584
loading story #50567156
loading story #50565313
loading story #50569466
loading story #50571858
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.

loading story #50568498
loading story #50569862
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

loading story #50565239
loading story #50565368
loading story #50568511
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!
loading story #50569457
loading story #50564973
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 :(
loading story #50566735
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.

loading story #50565045
loading story #50564787
loading story #50565381
loading story #50565989
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?
> Genuinely a massive moment in human history

Is it? It looks more like a forgettable moment to me. We're talking about an IPO, how many headline-making IPOs can you actually remember?

> as a SWE the gravy train is basically over in my view

That is not a result of the IPO even if you are right, and I have my doubts.

> they figured out how to make a program that does the job

No they figured out how to make software that makes the job easier. How is this any different from the introduction of optimizing compilers or type systems or any of the other software tools we all use? It makes programmers more productive, which means programmers can take on larger projects.

Coding agents have limits and the managers who forced their SWEs to use them are starting to figure that out. Using agents to both write code and review code sounds cool in theory but in practice it is not such a great idea -- it means that nobody actually understands the codebase and therefore nobody can actually debug the code when things break. No, you cannot just assume that you can also throw an agent at the problem when things break -- because the breakage might mean you lost access to the agent or the agent lost access to your system and cannot help you.

> difficult to grasp how much life will change in the coming years

Not too difficult to grasp. Shareholders will demand returns and Anthropic will have to deliver those returns. All the sky-high dreams about RSI and the next phase of human existence are going to evaporate and profit is going to be front and center.

Another possibility: Anthropic fails to survive the next recession and the companies that did not allow their employees to become dependent on Claude will be the winners.

loading story #50568773
loading story #50564923
loading story #50564630
loading story #50568186
loading story #50572309
loading story #50564741
loading story #50572314
loading story #50569493
contrarian opinion. I think all we’ve learned is SWEs are still very much needed. gas town failed, it failed quietly, but no one doing real work talks about software factories anymore.

Most companies that are running the “how many SWEs can we fire before it all breaks” experiment have learned it’s a failed experiment - this validated by every single major company/product outage where their uptime went below 90% this year.

I can’t help but think this anxiety and fear is just marketing. chill out everyone

It is strange this is the contrarian opinion when most of the evidence points to it being the case. Everyone working is busier than ever, more prs but no end in sight to the backlog still and fires to put out every day. PMs and designers who have deeper idea of product then most can put up some automatic prs for quick fixes, everyone with a bit of time can build siloed dashboards on their own but actually doing the day to day eng work to keep things running or design a new service to integrate with the product…I’m not seeing it
I think my fear is rooted in knowing that the tech has moved way faster than humans can adapt to it.

So we are not waiting for the tech to get good enough, we're waiting for humans to understand and integrate it.

I don't work in tech, rather manufacturing, and our company is barely using any AI (or using it, but only like AI mode in Google) despite me knowing that we could easily use it to cut heads. The automation we are leaving on the table is huge.

But I'm not gonna be the one to go to my bosses and say "Hey, you want me to show you what we can do with SOTA models and agents?". For now I'll just stick to using my accounts to leverage my job.

loading story #50565204
loading story #50564528
loading story #50564481
loading story #50570459
I think there's a spectrum of being a SWE and what we're seeing is the ones essentially just writing boilerplate code most of their day have a very different view than those who are solving problems with software that require careful thinking and execution.

A lot of people seem to think they can pick up an LLM and suddenly write software solutions as good as a seasoned SWE. But it turns into this terrible mess that's thrown out all engineering fundamentals, solving the symptoms instead of the cause.

If I were just writing boilerplate code with an LLM all day I'd be very scared for my job too.

loading story #50566017
loading story #50564538
>gas town failed quietly

This is a big problem. When this kind of thing gets launched, its all fanfare, this is the future, get on the boat or die.

But then it fails miserably and its like it never existed

Remember prompt engineering? Even skills and specs seems to be slowly dying.
loading story #50566361
loading story #50564858
loading story #50564935
loading story #50564693
> I can’t help but think this anxiety and fear is just marketing. chill out everyone

Here are few anecdotes:

1. I've a friend who owns a PT (physical therapy) business. He's not even a tech guy, but uses claude to manage most of the business aspects, and he has told me repeatedly that he would've to spend thousands of dollars to get things done, and instead he pays 250 per year.

2. Another friend is smart, and is a jack-of-all-trades type in the software/hardware/firmware business. He is solo bootstrapping by doing all the things from pcb to webapp. He doesn't see hiring anyone for the niche business.

3. A 65 year old friend of mine who never in any tech career was able to build website for his side business (that website looks really good btw) and he now talks about json and ocr.

You are the one who is out of touch with reality.

loading story #50579616
loading story #50564542
loading story #50565464
loading story #50564416
loading story #50564728
I don’t disagree that regular people can now make some basic software, but if you’re doing anything real with actual scale or consequences, nothings really changed. and to be exact, "real" means that if something goes, wrong then:

there is massive lose in revenue for a business and or infrastructure that people rely on goes down

if you’re working anything in this way, no one is just trusting a clanker. some thought leader might say the world is trusting an AI, but it’s not true. every company internally that is more than 2 people isn't trusting a bot, and it's well understand that it's a horrible idea (even by regular bullish AI business heads)

so yes, I have the bot help me write a basic website for me, and it can one shot the typescript express app-layer boilerplate for me, but if you’re serving even the most basic app at scale with consequences, the bot isn't mitigating the concerns and engineering decisions that go into this work.

a concrete real world example: literally msft outlook went down a week ago. it was out for god knows how many actual hours. it still might be partly down tbh. this is technology that is “solved” and is dumb simple in terms of complexity. their product was out for 48+ hours. and the status messages shared publicly by the engineering team did not only convey incompetence, but to paraphrase, the message they sent out was along the lines of, “We think we found the source of the problem, but unsure, the problem might be larger”

how much you want to bet they had a team of 30+ engs running around with claude asking the equivalent of, “please fix outage, no mistakes”

I’m still not convinced the outage is fully recovered because I still get errors.

point is, yes there isn’t a giant 100 football field wide moat between regular people and programming anymore. smart people can do basic stuff and less inclined people can build a static website now. if you’re worried about that, go study more and you'll learn the depths of this field go WAY beyond typing code

EDIT: typos

loading story #50564825
What does all these proved? If you don't have the budget for SWEs, you probably don't need one all. All these examples don't need complex engineering, Claude is a good solution to them (I doubt it though, if they really need something and it can make them money, it's always more efficient and cost effective to just hire someone for it) but it doesn't mean all businesses don't need SWEs anymore because everyone can be their own SWE.
loading story #50568869
loading story #50566420
I agree, but to the extent I’m worried about the future of the profession, it’s because I don’t know how much more the models are going to improve. Today’s models desperately need a real SWE in the loop to do most serious engineering. Will that still be the case in 5 years? I really don’t know
I think integrating libraries into a product will be essentially free. Novel solutions that require an understanding of the problem space to such an extent that unorthodox solutions seem viable is still the limit in my experience. LLMs, at least in my experience, need lots of guidance when the solution you want is not something that has already been done. If you look at it from a business perspective- most software shops have a small proportion of their software that is truly unique and their USP - the rest is not necessarily boilerplate, but definitely not bespoke and unique. This overhead will now be cheaper. Similarly, software vendors that dominate despite not having any bespoke, unique software component will soon have a tougher time. Why would someone pay for atlassian products now? All of their products are not good software- they have market dominance. Replicating their features will be trivial. Anyone who will be sufficiently fed up with paying will DIY the solution.
loading story #50565552
loading story #50564879
I feel like once it doesn't need an engineer in the loop, does it need ANYBODY in the loop? at that point the whole company can probably be autonomous.

That seems like it would be such a paradigm shift that the second and third order effects are so crazy and nobody can predict what that world will actually look like

{"deleted":true,"id":50564276,"parent":50564097,"time":1795113712,"type":"comment"}
loading story #50565353
loading story #50566409
IMO models are getting smarter at software, but not at software engineering.
> it’s a failed experiment - this validated by every single major company/product outage where their uptime went below 90% this year.

This is engineering thinking, not business thinking. The question is, did the uptime drops cost the company more money than the firings saved? If the answer is no (which for megacorps like Microsoft it is) then the experiment was a success.

Business thinking relies on a hell of a lot of engineering thinking to survive. If your services and infrastructure you depend on to do your business fail, you don't have a business.
loading story #50565521
I didn't know gas town failed. What happened? Did Steve yegge say as much?
Most developers built their own framework /harness anyway
projects like gas town are failures if they don't become a standard practice or a truism in the tech scene. thought leaders are never going to announce their ideas as failures so they can maintain relevance, as well as plausible deniability about it's success/failure
> I didn't know gas town failed. What happened? Did Steve yegge say as much?

He wrote a series of blog posts in which he talked about how Gas Town failed and blamed it on Opus 4.7 changes causing all his workflows to fail. Then he announced Gas City as a rewrite.

At some point after that he seemed to give up on the whole idea and instead just started working on reviving an old graphical MUD style game he made where I guess now he spends $10,000 a month on agents to build a game that currently has 0 concurrent players (4 concurrent 24 hour peak) on Steam:

https://steamdb.info/app/1541710/charts/

The game is available from other platforms than Steam so maybe he's got a bit more users than that across the platforms, and his stated plan is to bilk "whales", so maybe that's working out for him? But it still seems like he's lighting massive amounts of money on fire in what appears to be a prolonged state of ai psychosis.

Must be nice to be that financially secure.

Hey you only need 1 whale at 10K / month to break even
loading story #50566468
loading story #50568149
Failures are nearly dead silent aside the million words of hype. There is no accountability for "gassing" up so many people and taunting them that if they don't get on board a failing idea then they will be left behind. A lot of grifters get off freely.
Gastown was too early and focused on the angle that having agents cosplaying a mini org chart was the way to get better results.
this is the only reasonable opinion. people saying "they made a thing which does the job" just fell to the hype mindlessly. someone still needs to input stuff into a thing which does the job, this someone is SWE or systems analyst. not everyone is a good systems analyst and can turn business goals into a clear specification to implement.

if the hype was all true, i could just prompt the llm to make me money and it would be able to do it, but it's not possible

Are they bringing their employees back in the same numbers and for the same wages though? Or are they outsourcing to Indian humans-in-the-loop for 1% of the cost?
Some are keeping the onshore senior engineers / architects and using the LLMs / agent-harnesses to replace the offshore.
Depends what quality of work they want? Hopefully they've learned their lessons in the first outsourcing craze, before AI lured them to another ride on the same carousel.
loading story #50564820
I think it has changed everything and in all honesty it has been the biggest change since the introduction of high level languages (As in from Assembly to C and Algo).

but at the same time I think the companies are pumping this idea that SWE is over and stoking anxiety and we have yet to see how bad things get when everyone can write software without thinking about it, we will see what insecure slop gets produced and it's going to be huge.

The issues with AI security are quite big as well, people who will rely on just an LLM to be the intelligence will get burnt I am sure especially in operations, prompt injection is still an issue, would someone running LLM's notice an provider endpoint getting hijacked and acting maliciously and inserting malware into production servers.

The future is going to be a strange one for sure but being able to turn your brain of and get your LLM to run you servers write you servers is not going to work alone.

I have also yet it write a good fairly novel program without babysitting (quite trivial babysitting sometimes) but stuff that is bread and butter for us, for those who don't have those skills, will they really know how to explain the issues they may run into that requires creativity, for example telling it to hack something together with curl and jq, knowing why a certain thing with the sandbox is not working.

I think these issues are not as easy to resolve with just better tooling and they will soon get annoyed at prompting.

Additionally I think Gas Town shows the sort of almost mentally ill mentality that is baked into some of these tools and ideas, Everything I read of Gas Town was so strange and the amount of tokens used to anthropomorphize agents.

Some of these staff reductions are also due to the ENORMOUS pull of the US IT sector. There are not many companies with as many SWE as Microsoft and Meta, so some reduction isn't that surprising.
Software is needed, not SWEs. I can now run a company without having to hire any pesky humans doing so called "software" work. No need to worry about their health insurance, 401k, PTO, 1:1, "how are you feeling" and all such nonsense.
> but no one doing real work talks about software factories anymore

My friends at FAANG companies would disagree here. If anything, it seems to be the exact opposite.

Sure, it's not a end-to-end 0 touch factory, but a majority of folks I talk to these days that I consider good engineers aren't writing _any_ code anymore. They do that as a hobby outside of work.

loading story #50564694
loading story #50565240
Non-FAANG, I don't have the luxury of product owners and designers who know the ins and outs of systems to present well-specced requirements docs. Or Jira tickets that aren't absolutely full of default-style Claude slop. It's not that I don't have my own slop factory which implements as-written, maybe bringing me into the loop for the most non-trivial decisions, and takes it through test, MR, and to production staging... but most of the interesting cases I pick up really do need a human to make the non-trivial design decisions. I've seen the garbage that these SOTA models put out when nobody's at the gate.
loading story #50563820
AI is not even close to replacing SWEs.

AI can write syntactically perfect code but barely has a sense of architecture.

It needs tons of 'guide wires' to keep it from going off track.

Unless you're building basic SaaS, it's still a 'research and coding assistant'.

AI has never produced non-messy architecture that I did not have to go in, re-think and guide a re-write.

loading story #50564837
loading story #50565649
loading story #50565603
loading story #50569432
loading story #50566000
loading story #50565723
loading story #50566765
The market for software hasn't disappeared. The way we build software has changed. AI can write code. But someone still needs to talk to customers, gather requirements, write specifications, generate code, build, test, debug, deploy, secure, market, sell, support, monitor, be on-call, handle incidents, track bugs and so on.

The business of software still exists and it needs to people to run it. It will require fewer people than before, and as a result cost of software will come down. There will be increased competition, and big SaaS companies will face fresh competition from upstarts. As a result there will be pressure to innovate.

AI can't innovate. This is one of the key limitations of AI. Not all humans can either. But those who can will be in increased demand.

As software becomes cheaper, the total consumption of software increases (See Jevons paradox.) Cheaper development makes smaller markets viable. There will be software available to meet needs that are unmet today because the market is too small. This will increase the number of software jobs. It won't all be coding jobs, it will be jobs that run the software business (see first paragraph).

loading story #50571265
loading story #50565799
loading story #50565573
If SWE is over let's follow the chain of thought. A company has no SWE in it. Who is shipping and maintaining the software?

2 options:

A) A real person with a job title that's not SWE. Will it be managers / product managers / business owners / something else? Whatever the job title, those people need SWE skills and experience to manage the agents. It is a very high ask for non-SWE job title to absorb both the skill and time commitment to drive AI-first software work.

B) AI Agent. But how does the AI Agent get setup with what it needs to run in a loop, who investigates and steers the agent course when it deliver something that doesn't work? It will needs someone SWE skills/experience.

In either case sounds like you need someone with SWE skillset in your company... so not sure why the job would go away.

I think we long passed the massive moment. Right now, it looks more like an attempt to save the sinking ship. I think Anthropic and OpenAI they hit the wall in their business. Yes, in the last 4 years, we got a massive disruption in our industry and we work with the highest abstraction ever. But I feel like SWE was always moving that way.

Now, I only see how AI tools stagnated in the last few years. To me, Opus 5.x solves all the issues I've had with programming. I no longer need more. They also failed with massive adoption of non-tech people beyond using AI tools as simple guidance and search tools with some simple programming capabilities.

I don't see any way for them to grow more (maybe I am blind), and open weight models are only going to get better, which will sink them further.

Only time will tell I guess.

Have you actually tried vibecoding something not firmly on distribution? I'll give an anecdote.

I've been building for the past few weeks a fancy text editor for myself to work with AI in a more sustainable and sane way. I don't have much time for this, so I've entirely vibecoded it: I don't look at the code and I've provided only some initial design and engineering decisions, debug hints, etc. on top of natural language feature requests.

For about a week using the strongest Claude models (Fable 5.2 and Opus 5.5) this went great, and I had a minimally functional tool that worked very nicely. It seems that I hit some sort of complexity ceiling for those models though. The second week, every feature I try adding creates a new type of jank that can (at least by me) be only vaguely characterized. Most recently inserting into a line (even in the middle of the viewport) causes the viewport to jitter about.

Our work will change, we will spend less time on tedium, we will become more ambitious. Barring an architectural paradigm shift we will still need people with strong engineering and design instincts, and even more importantly the ability to write reference code and formal specifications codifying desired behaviors.

loading story #50564224
loading story #50564146
loading story #50564523
loading story #50569883
loading story #50564240
loading story #50564307
loading story #50564173
loading story #50564292
loading story #50564363
loading story #50564117
loading story #50564289
loading story #50564124
loading story #50564139
Software engineers are the best at using ai agents, the gravy train is just getting started.
Look up jevons paradox, you may feel better.

At my current company - not a software company but we have a dozen plus software engineers - and while we are expecting them to get more done, and their productivity is increasing dramatically, the list of things we want them to do is growing faster than they’re finishing things.

Things that were huge projects, that would have been hugely expensive for us to do, are now affordable and can be done in a couple of months or days, it’s no longer the most important things get the developers time, but now people in HR, finance, etc are getting their projects “on the list”

About two years ago - I had the view that AI was torching what was fun with software. Eventually I realized that I get a team of improving engineers that helps me make our thoughts a reality faster. Yes - they need guidance, and direction, but that's no different than what I've been doing for 20 years.

Now, the real difference is whether I write the code in English, Python, Go, C++, etc. The new tooling (AI) forces me to express and crystalize my thoughts in natural language - and it ends there. Design documents, consensus, feature exploration, testing, knock on thinking.. these are actually now MORE important than before. I've outsourced the mechanics and syntax of writing code but not the organization, design, and layout for scale.

This is pretty awesome.

loading story #50571301
loading story #50568451
loading story #50564898
You need to learn how to build a software factory. How to guide the AI to do the right thing with good taste.
loading story #50563964
loading story #50563873
loading story #50563775
loading story #50564109
loading story #50563735
loading story #50563745
loading story #50563733
loading story #50564220
loading story #50568482
loading story #50568034
If there comes a point when an LLM makes the SWE profession redundant the blast radius is going to be much bigger than that, so you won't be alone. For now, there is still plenty of work to do and for certain job categories I would say there is actually more work at the moment.
I dub thee Product Engineer. You no longer need read nor write arcane symbology for logic. You are now emboldened to describe application behavior and design. You still claim architecture with data and views, events, and more. Move through this new future with confidence and authority.
loading story #50564887
loading story #50565146
loading story #50564148
loading story #50565524
{"deleted":true,"id":50564466,"parent":50563691,"time":1795114395,"type":"comment"}
loading story #50568576
What a feeling to lose our superpower! But what draw us into building in the first place was our curiosity with tinkering. We got lucky it became so profitable, but I’m sure we’ll find a way to adapt and thrive again.
loading story #50565949
loading story #50566762
loading story #50566732
It doesn’t do the job. It’s a program. Humans do jobs. Humans will continue to do jobs.

What Anthropic has excelled at isn’t engineering. It’s convincing your boss that you can be replaced with a Claude Code subscription. Just look at the leaked Claude Code source. Or read their “engineering,” blog. It’s all marketing glitz.

The reason for all this marketing is because they rent their compute and they need every software developer to need them. They need us to depend on them to do our jobs. Because this isn’t a profitable venture. It’s resting on a house of cards.

Anthropic has to deal with the very real possibility that their providers go under. And that other harnesses on alternative models get better, cheaper, etc. People seem to be pretty price sensitive after the token-maxing rush didn’t work out.

I think there are still plenty of reasons to believe that our profession isn’t going anywhere. Changed, sure. It always changes. But it’s not over and it’s not, “solved.”

loading story #50568952
loading story #50563959
The need for engineering will not go away. The job will change, yes. But if non-technical folks can stitch something together with LLMs, technical folks can still do it better, quicker, and more reliably. Maybe the job boundaries will become more fuzzy, in both directions, but I just don't see a company running software without having techies in the long run.
The work wont end, but it will be different. It will be a turbulent time, and it will take effort to stay up to date. Disruption isn't forever, it comes in waves. Things will eventually calm down. Try to make sure you are in a good place when the time comes.
loading story #50569861
loading story #50564258
loading story #50565034
loading story #50570409
loading story #50566010
I regularly use two applications that I know are built by developers using Claude, and there are consistent bugs in the user interface. Really stupid simple stuff that an experienced dev would know to check for and fix.
loading story #50566818
loading story #50564829
Its all white collar work its just that software development was low hanging fruits thanks to the extreme amount of training data, its basically text, its also friendly for an llm because the compiler acts as a corrector if something is wrong. so its ok if its not entirely right. Since SWE is dying all SWE companies are panicking and trying to sell AI enabled software that will automate all other jobs. There is an extreme demand for that because all businesses want to dump employees to get higher profit margins. So you are not alone. within a couple of years there will be a total economic collapse. Unless something drastically is done https://www.ethicalacceleration.org/
loading story #50565089
loading story #50568340
loading story #50564188
I see agents as horsepower. You still need engineers to drive it. And drive it in right direction.

I'm not scared for the future of software engineers and computer scientists.

Where I live we now have the Waymo cars driving around all times of day and night mapping the local roads and traffic. There are literally tens of thousands of recent immigrants in the same city who rely on taxi driving as their only marketable skill in a rather xenophobic and old-school employment market. They are going to be very angry indeed in a few months when self-driving taxis take their jobs. There's no doubt AI is going to have the most profound impacts in almost realtime in places where it hasn't even made an appearance yet.
I think standards / requirements for security and software quality may sky-rocket given the automated hacking stuff...
loading story #50565709
loading story #50567653
loading story #50568321
loading story #50564397
loading story #50565253
an IPO is a massive moment in ALL OF HUMAN HISTORY! The stock price seems to agree with you: https://www.cnbc.com/quotes/ANT/
loading story #50566214
loading story #50570361
loading story #50568615
loading story #50566456
loading story #50564996
loading story #50569148
> Genuinely a massive moment in human history

Massively sad moment, a few handful of already well to do individuals got even richer, allowing business to cut wages. Sure it’ll create new jobs / industries but the short term impact is not something I look forward to.

There is so much division in the comments, while we keep bickering someone is eating all the cake! This fictional division between humans is maybe the greatest success of the people in power in this century.
loading story #50565654
loading story #50566496
loading story #50564974
loading story #50564956
You are now an architect.

Everybody is an architect now.

Don’t worry.

loading story #50563917
loading story #50580285
loading story #50563818
loading story #50564758
I wonder if this is how Lee Sedol felt.
Thankfully you've been saving and investing and can now buy a slice of the pie, right?
The Gravy Train narrative is curious. The highly-paid programmers in the US earned their companies a lot of money. Was it a gravy train for them or for their companies? Judging by the ratio of maybe earning 1 Million for a one 100K cost-of-employing programmer that is just floating around in my brain, I’d say the companies. There was also the no-hire collusion among big companies.

The programmers were/are simply capable and in relative short supply. Even with that they earned the companies massive profits. (I have completely different issues with my high-IQ nerd peers... more what they were working on.)

Now the parasite companies can simply harvest all of that value for nothing. Big Tech is moving from a gravy train to a free ride.

Defintely a very Capital Guy perspective top comment.

> as a SWE the gravy train is basically over in my view. they figured out how to make a program that does the job.

They certainly did not. LLMs are way worse than a competent human programmer.

> difficult to grasp how much life will change in the coming years.

More prosperity than you've ever had.

loading story #50565638
loading story #50565860
loading story #50566381
work will scale but there will be no free lunch anymore.
loading story #50565764
It's a new tool to build with.
Why is the stock listing the moment and not the moment the thing actually existed?

2/5

loading story #50568892
loading story #50568870
Halting problem and busy beaver shows us that there is an Unbounded amount of programs to build for reifying and automating business processes as well as advancing technology further

The gravy train is just starting

Lol. Yes they and 100 others including all the open source models. There is no moat
loading story #50566736
loading story #50565976
loading story #50565847
loading story #50565377
I don't know it's possible the industry shrinks down to pre 2005 levels of staffing since all the layers of jobs that got created over the last 20 years become less important and disappear.
I haven't programmed by hand (I use vim) since late 2024, so about 2 years now because of AI. I've been building coding agents since 2021. As someone who coded by hand for 30 years, writing code has always been about 5% of the work and AIs do that well now. The coding agents can also do some of the other 95% of the job but not as competently.

I have seen coding agents get better as both the models and harnesses improved. I used to have to manage context by hand, I used to review every line. I no longer do.

However, I will tell you this from my experience with AI. Software is not any easier. The same complexities are still there. What's different isn't the kind but the scale. A 2 person team can do what a 20 person team did 5 years ago.

What is still required is a shit ton of feedback to build what you want. It's still hard to build complex software even with AI. In fact in some ways harder because AI agents will go down rabbit holes and create entropy faster than you can say Bingo.

Productivity is waste, it has to be, it's thermodynamics. The person's job is to fight entropy in the system. That has been true before AI and true today.

We have to remember, software is there to serve us and fix our problems. AI doesn't change that.

loading story #50564234
loading story #50564392
loading story #50564403
loading story #50564113
loading story #50564140
loading story #50567101
Do what I did: marry a surgeon. I'm sure her job will take longer for them to automate, might give us enough time to retire before the world goes to complete shit.
It's a massive thing, for sure, but given that Anthropic has no plans for profitability it's just one more exhalation into the bubble.
Every single time I use AI (which is every day), regardless of the model or harness (which is pretty much always Opus 5.5 or Fable 6.2, with Kiro or Claude Code), the LLMs do complete and utter rubbish to the point where they would be genuinely harmful if left to run write commands unsupervised.

Just today Opus 5.5 tried to send a Slack message to one of my teammate when it had to edit a code file. When asked why, it said it just "picked the wrong tool".

LLMs are borderline useless, AI has led to 0 increase in actual value produced. It's all powder in front of our eyes.

I genuinely cannot take anyone seriously when they say they're afraid of being replaced by AI. The only explication possible (unless they're astroturfing), is that they literally never look at what LLMs produce and always run in "Trust all tools" mode without ever looking.

The people who are most bullish on AI are the people who aren't hands on with the material. I'm hands on with AI all day. Its like a bunch of junior devs who never learn or mature or grow. With a Junior dev a teachable moment generally sticks. The AI never learns, even if it makes a "memory", it will straight up ignore those memories at the slightest convenience. AI is shit, but I use it everyday, much in the same way that Javascript is shit but I use it everyday.
loading story #50565722
Yeah it’s a remarkable black swan. SWEs were turkeys after all. Fed well, taken care of, and comfortable. Thinking they’re the lucky ones; this is the life. How nice.

It’s a dark coincidence that “Turkey Day” is next week in the USA. Many turkeys that will be on our plates never imagined THAT fate.

The writing was on the wall. First wave was the Nocode thing, that clearly outlined what they wanted. Then lowcode, and now vibecode.

The gullibility of people is astounding, and they never learn.

Needlessly negative. If your job can be replaced by a program, what kind of an SWE are you?
loading story #50563752
It doesn't matter when there are not enough jobs for 8/10 employees. Try getting a reply, much less an offer, from anyone in this environment.
Overall unemployment is still fairly low.

(And I'm getting lots of job offers. But I'm in Singapore, and that's presumably not where you are.)

"Overall" doesn't help older tech experts right now. Put your money where your mouth is, and send me one of those. ;-)
loading story #50567856
loading story #50563857
loading story #50563748
loading story #50563738
loading story #50563790
loading story #50568734