News for hackers. Stuff that matters.
Re:Software engineering may no longer be a lifetime career by doug_durham on Monday May 11, 2026 @01:26PM (#48097907)
This is a bit of glib answer. Most of the time is spent coding which encompasses typing, retyping, and retyping again. It also includes banging your head against the wall while trying to get one of your rewrites to work against and under-documented API.

OP's formulation makes SWE sound like a purely noble enterprise like mathematics. It's more like an oil rig worker banging on pieces of metal with large hammers to get the drill string put together. They went in with a plan, but the reality didn't agree and they are on a tight schedule.

Re:Software engineering may no longer be a lifetime career by estebank on Monday May 11, 2026 @01:37PM (#48098053)
Most of the time is spent figuring what the right thing to do is, not writing the implementation. Sometimes the process of writing the implementation surfaces new considerations about what the right thing is, but still, producing text to feed to a compiler is not the bulk of the work of a software engineer. It is to unearth requirements and turn them into repeatable software.
Re:Software engineering may no longer be a lifetime career by powvans on Monday May 11, 2026 @03:00PM (#48099214)
Feels like lately most of the time is spent arguing about or at least worrying about whether or not AI is going to replace all software developers.
Re:Software engineering may no longer be a lifetime career by pydry on Tuesday May 12, 2026 @12:31PM (#48110566)
Or dealing with the idiotic fallout of somebody who sucks at coding or even has never coded in their life trying to make that happen.
Re:Software engineering may no longer be a lifetime career by 7e on Monday May 11, 2026 @03:55PM (#48099847)
If you’re spending time thinking and not experimenting, then it’s because experimentation is expensive. With an LLM you don’t have to try to predict a complex system in advance, experiments are so cheap to can just converge to a solution directly. None of this pontificating; it’s really not that useful anymore.
Re:Software engineering may no longer be a lifetime career by GolfPopper on Monday May 11, 2026 @04:01PM (#48099919)
And before long you have a solution that is made up of a thousand pieces of spaghetti that neither you nor anyone else understands. And when your solution becomes too brittle to use, cannot be maintained, or fails catastrophically, then what? Just hope that's someone else's problem?
Re:Software engineering may no longer be a lifetime career by gchamonlive on Monday May 11, 2026 @04:20PM (#48100167)
Refactoring is cheap too, but you have to read your code and know when to stop and ask the agent to refactor, rewrite, adopt or change libs, fix issues presented by linters and code quality scanners, change abstractions and rethink the architecture.

It's never been easier to replace chunks of code with sane software patterns, but you have to have a feel for those patterns. And also understand what's under the hood.

You folks speak like the only function of the agent is to spit code and features. Get a grip and treat your deliverables with care, otherwise you only have yourself to blame, not the AI.

Re:Software engineering may no longer be a lifetime career by microflash on Tuesday May 12, 2026 @04:32AM (#48105694)
Refactoring is not cheap when you take into account the cost of not breaking things.
Re:Software engineering may no longer be a lifetime career by gchamonlive on Tuesday May 12, 2026 @05:16AM (#48105956)
When we say "X is cheap" it's in comparison to doing things manually, not irresponsibly
Re:Software engineering may no longer be a lifetime career by a10c on Monday May 11, 2026 @04:23PM (#48100184)
That's the point. Your prototype doesn't need to be pretty. It just needs to prove that the value is there for it to be made pretty.
Re:Software engineering may no longer be a lifetime career by avador on Monday May 11, 2026 @07:59PM (#48102389)
Order of operations: Make it work. Make it right. Make it fast.[0]

[0]: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...

Re:Software engineering may no longer be a lifetime career by didgetmaster on Monday May 11, 2026 @10:22PM (#48103461)
Unfortunately, too many developers (especially in the AI era) stop after the first item.
Re:Software engineering may no longer be a lifetime career by snvzz on Tuesday May 12, 2026 @02:53AM (#48105071)
Stop... short of.
Re:Software engineering may no longer be a lifetime career by megous on Monday May 11, 2026 @06:47PM (#48101760)
You actually get what you ask for. And you can ask for anything, vaguely or not.

You'll end with spaghetti if you'll play a bad manager and only ever allocate time for new features and never for cleanups.

You can go through code, add REFACTOR comments based on your tastes and thoughts, and get your result and iterate to your heart's wishes. You just don't need to do the direct code typing.

Re:Software engineering may no longer be a lifetime career by dasil003 on Monday May 11, 2026 @04:23PM (#48100193)
This is very naive and reductive thinking. Experiments have a cost, you really have to think carefully about what you are trying to learn. Even when code is cheap, traffic and time are still huge constraints, and you better make sure your hypothesis actually makes sense for your goals, because AI is more than happy to fill in the blanks with a plausible but completely wrong proposal.

More broadly, it's well understood that experiments are not a replacement for design and UX. Google is famously great at the former and terrible at the latter. Sure the AI maxxers will say the machines are coming for all creative endeavours as well, but I'm going to need more evidence. So far, everything good I've seen come from AI still had a human at the wheel, and I don't see that changing any time soon.

Re:Software engineering may no longer be a lifetime career by avador on Monday May 11, 2026 @07:47PM (#48102321)
I think you and 7e are both right. Being able to iterate some N orders of magnitude quicker is a big deal. This doesn’t eliminate design and UX. Rather, it merges it with high iteration speed to produce a form of “play”.

“Play” is what produced at least two (likely more) generations of attentive (and therefore competent) programmers. The hype around LLMs is painful, yes, but attentive human minds will ultimately bust through it.

Re:Software engineering may no longer be a lifetime career by vintermann on Tuesday May 12, 2026 @01:56AM (#48104715)
Even writing code the good old way, of course we experiment. I remember the old rule "Plan to throw away the first one. You will anyway." But then there's the "second system effect" where the second system is supposedly always overengineered and trying to take every possibility into account.

And then there's the times when the quick sloppy poc you planned to throw away gets forced into production and is still impossible to change ten years down the road.

AI makes all these problems so much less painful.

I worked at a company which had a huge monolithic ERP system (their product, to be clear) with no good separation between the GUI layer and presentation layer. The GUI was also dependent on an ancient version of the Borland C++ compiler. They put in a humongous effort to move to a slightly more modern UI library, and a client server architecture.

However, someone had decided that messages in xml or json were too inefficient, they already had performance issues. So they went with a binary message protocol of their own design - with no features for protocol update. Everything communicating with the server had to be on exactly the same version, or it would throw an error. So of course they very, very rarely updated the protocol.

I think the best help of AI will be to clean up such real life messes of soul-crushing architectural regrets. Will it do it perfectly, certainly not, but I wouldn't do it perfectly myself either if I was forced to do it - and I'd take a hell of a lot more time to do it.

Re:Software engineering may no longer be a lifetime career by antonvs on Monday May 11, 2026 @04:58PM (#48100589)
> If you’re spending time thinking and not experimenting, then it’s because experimentation is expensive.

No, because no amount of experimentation can solve many of the problems that have been solved by thinking. Even your claim about "experiments are cheap" requires thinking to decide what experiments to do. No one is generating all possible solutions that fit in X megabytes; you have to think to constrain the solution space.

Re:Software engineering may no longer be a lifetime career by jimbokun on Monday May 11, 2026 @05:41PM (#48101040)
So the infinite monkeys with infinite typewriters approach.
Re:Software engineering may no longer be a lifetime career by darepublic on Monday May 11, 2026 @07:26PM (#48102125)
aka "swarms". cool sounding name for.. throw yet more mud at the wall. at unprecedented scales
Re:Software engineering may no longer be a lifetime career by Silhouette on Monday May 11, 2026 @09:45PM (#48103211)
With an LLM you don’t have to try to predict a complex system in advance, experiments are so cheap to can just converge to a solution directly.

We saw a similar philosophy in TDD advocacy many years ago. Search for something like "Sudoku Jeffries" to see how that went. Then search for "Sudoku Norvig" to see what it looks like when you actually understand the problem.

The idea that you can somehow iterate your way to a solution when you have no idea where you're trying to go or even which direction your next step should be in has always seemed absurd to some of us but in the era of LLMs there's no longer any doubt. In the agentic era (can we call a few months an "era"?) I estimate that 90% or more of the writing I've read about how to use agents most effectively came down to making sure there is a clear specification for what they need to implement first and then imposing extensive guard rails to make sure their output does in fact follow that specification. It's all about doing enough design work up front to remove any ambiguity before coding the next part of the implementation and almost everyone claiming any sort of real world success with coding agents seems to have reached a similar conclusion.

Re:Software engineering may no longer be a lifetime career by stuaxo on Tuesday May 12, 2026 @05:29AM (#48106020)
Well - you converge to a system, but do that by pruning what you don't want.

If you care about maintainability and quality (and I include maintaining using LLM based tools) then you need to understand what it does (in doing so you will find lots of things for it to fix - you'll probably find that the architecture it's chosen is not right for what you want too).

Re:Software engineering may no longer be a lifetime career by imtringued on Thursday May 14, 2026 @02:40AM (#48131895)
I've noticed that a lot of developers fall into a trap where they start a project or experiment because their mental model is that an LLM made the task effortless, but in reality they ended up spending more time, because they committed themselves to doing projects that bring correspondingly less value such as throwaway prototypes.
Re:Software engineering may no longer be a lifetime career by eweise on Monday May 11, 2026 @06:28PM (#48101566)
AI is pretty good at figuring out what the right thing to do is.
Re:Software engineering may no longer be a lifetime career by incanus77 on Monday May 11, 2026 @06:32PM (#48101601)
AI is pretty good at pulling from the body of existing solutions of what the right thing to do is.
Re:Software engineering may no longer be a lifetime career by mkoryak on Tuesday May 12, 2026 @01:44PM (#48111649)
I find that it often pulls a solution that is good enough for this problem today. Sometimes that is great, and other times it's just creating a pile of shit
Re:Software engineering may no longer be a lifetime career by CyberDildonics on Monday May 11, 2026 @07:35PM (#48102225)
AI is decent at solving problems that lots of people already solved a long time ago.
Re:Software engineering may no longer be a lifetime career by didgetmaster on Monday May 11, 2026 @10:29PM (#48103515)
Too many people believe that AI is going to come up with elegant solutions to problems that no one has ever solved before. Maybe someday, but for now it seems to be good at finding a solution that may be hidden away somewhere in stack overflow. If it just isn't there, then you are out of luck.
Re:Software engineering may no longer be a lifetime career by munksbeer on Tuesday May 12, 2026 @12:17PM (#48110369)
There is almost nothing new in computer programming. 99.999% of any code most of us on this forum write will be repeating patterns that have been written thousands of times before.

Tell a coding agent what your new thing needs to do, give it the absolute constraints, max response times, max failover times, and so on, tell it which technologies it has access to or could use, and then tell it to spend a lot of time going over and over the design, coming up with an initial X number of designs (I use 5), and then it must self criticise each one of them and weigh them up, narrow down to three, before finally presenting those three options to the user.

Now you read the options, understand them, realise that the AI has either converged on something very sensible, or it has missed something, so you tell it what it missed and iterate. Or it nailed something good, you pick the option you prefer, and tell it to come up with a more fleshed out high level design, describing the flow and behaviour deeply (NO CODE REFERENCES!). Then once you're happy, tell it to use that and write a comprehensive coding plan. Tell it specifically what coding patterns you prefer (you should have these in your AGENTS.md file already), what patterns to avoid (single threaded? multi-threaded? Avoid gc? How you typically deal with error conditions, etc etc).

Then have it start iteratively working on the coding plan, and it *MUST* have a strong feedback loop. If there is no feedback loop initially, I tell it to build one. It must be able to write very fluent integration tests (not just unit tests). It must be able to run the app and read the logs.

Do all this and I bet you get a better result that 80% of developers out there. Coding agents are extremely good when used well.

Re:Software engineering may no longer be a lifetime career by ecocentrik on Monday May 11, 2026 @02:43PM (#48098986)
Glib is called for. The amount of information asymmetry that's still on the table as vibe coders and vibe engineers and vibe doctors emerge is staggering. Professional experience is still incredibly valuable. Most software developers might spend more than 6% of their time coding but no senior developers are banging their heads for hours over typos.

https://www.youtube.com/shorts/xBilK3gT5e0

Re:Software engineering may no longer be a lifetime career by roncesvalles on Monday May 11, 2026 @03:43PM (#48099732)
These days nobody bangs their heads over typos.

LLMs evaporated 90% of the "moments of despair" when you have an error and googling it isn't helping, or googling it made you realize you have to read 30min of documentation.

Coding is a joy now. LLMs shaved off all the rough edges.

Re:Software engineering may no longer be a lifetime career by skeeter2020 on Monday May 11, 2026 @03:57PM (#48099867)
You can't possibly believe this, or you and me (and many others) are doing something different. LLMs have created an entire new - huge - set of bang-your-head moments, as they go off half-cocked in a million simultaneous directions, chasing their tail, or just making shit up. And since the vast majority of work is on existing - often ancient - codebases, let's find out if you feel the same way in 18 months.
Re:Software engineering may no longer be a lifetime career by GolfPopper on Monday May 11, 2026 @04:04PM (#48099956)
LLMs are great for anyone who isn't responsible for the consequences of what they code.
Re:Software engineering may no longer be a lifetime career by jimbokun on Monday May 11, 2026 @05:42PM (#48101053)
Give them work in smaller chunks.
Re:Software engineering may no longer be a lifetime career by lo_zamoyski on Monday May 11, 2026 @06:27PM (#48101548)
Maybe I'm weird, but my usage has been very conservative. As in, I treat the LLM like a junior dev that I have to micromanage and handhold.

I am terrified of allowing these things to complete tasks end-to-end with nothing intervening. Maybe that's why I don't run into many of these issues. I mostly delegate grunt work and manual tedium, not reasoning or design choices to the LLM. I may consult the LLM and ask for criticism, but there is no way I'm going to allow it to quietly make design decisions that I don't know about.

Re:Software engineering may no longer be a lifetime career by roncesvalles on Monday May 11, 2026 @07:16PM (#48102032)
That's only if you do agentic coding.

I use LLMs in the following ways:

1. Copy-pasting code into the web chat UI and asking for something (bugfix, add a feature, refactor, explain, review it etc), including entire source code files. A $20/mo Gemini subscription goes a long way (never been rate-limited). I only use the highest model. I often just copy-paste the entire source file between 3 backticks.

2. Cursor Tab. I do have hotkeys to enable and disable it; it's disabled most of the time otherwise it gets annoying.

3. Single-file changes directly from Cursor's AI sidebar. I only do this for simple, predictable stuff because even their auto-routing "Premium" setting is not as good as pasting stuff into Gemini 3.1 Pro.

That means I have only two $20/mo subscriptions: Gemini and Cursor.

I don't use Claude Code, it's really for people who don't know how to code. I don't use Plan Mode; I make and track the plan myself (if at all). I only tell the LLM granular tasks to execute. I don't use `claude.md` or `agents.md` or anything like that. If I don't like a particular output, I reset everything, modify my prompt and try again.

I believe this is the only way to fully leverage LLMs without losing any product quality. If you're trading off quality for "speed" (in quotes because over the long term, a low quality codebase is a massive drag on productivity) then there's no point.

Re:Software engineering may no longer be a lifetime career by avador on Monday May 11, 2026 @08:30PM (#48102635)
I _think_ what you’ve said is “go shallow, not deep”. That is, don’t let the walk you make inside the latent space a long one. Twenty-five short and peppered steps, from de novo, is better than one long, protracted stew.

Is that accurate?

Re:Software engineering may no longer be a lifetime career by roncesvalles on Tuesday May 12, 2026 @12:40PM (#48110694)
Well yeah. If you know what you're doing, why would you let the AI take control?
Re:Software engineering may no longer be a lifetime career by avador on Tuesday May 12, 2026 @05:45PM (#48115026)
Well, if it works on step one, then why not step two? Where would different folks draw the line? My grandparents might continue on a while, whereas I would not. But if it also “works” on step two for me, should I take a third?

What counts as “works” is the important bit, I think.

Re:Software engineering may no longer be a lifetime career by suzzer99 on Monday May 11, 2026 @09:47PM (#48103220)
Yes, if you're using them to write large chunks of code or entire features. If you just use them to clear up some trivial problem in an unfamiliar technology that you used to spend 30 minutes googling with 50 tabs open, or stuff like write a method to filter, map and reduce an array based on specific criteria, they're a godsend.
Re:Software engineering may no longer be a lifetime career by marcus_holmes on Monday May 11, 2026 @10:19PM (#48103443)
You are in charge of what the LLM does. If it's running off half-cocked in a million simultaneous directions, that's on you. Write better skills. Tell it not to do that. Break into its loop and ask it wtf it thinks it's doing. If it's making shit up, force it to test more.

The LLM will do what you tell it to do. Manage it.

Re:Software engineering may no longer be a lifetime career by ecocentrik on Monday May 11, 2026 @03:52PM (#48099817)
Languages have been reporting compile and runtime errors for decades. Additionally very few senior developers don't already have their minds wired to spot typos the way copy editors spot bad punctuation. Typos were only really a problem for students.
Re:Software engineering may no longer be a lifetime career by neutronicus on Monday May 11, 2026 @10:30PM (#48103519)
I've been writing C++ for almost 20 years at this point and I do still benefit from how good Claude is at gnarly Template error messages.
Re:Software engineering may no longer be a lifetime career by kibwen on Monday May 11, 2026 @03:57PM (#48099870)
> LLMs evaporated 90% of the "moments of despair"

And then condensed an equal quantity of despair out of the ether via confident confabulations.

Re:Software engineering may no longer be a lifetime career by taurath on Monday May 11, 2026 @04:18PM (#48100140)
Equal? No, no no no. Upper management is making PoCs that promise to solve longstanding multi year learnings of tradeoffs and solution balancing, and setting goals based on that. We are heading to a cliff and everyone is going to learn what happens when you replace already vulnerable foundation pillars with pig iron.
Re:Software engineering may no longer be a lifetime career by arcboii92 on Monday May 11, 2026 @04:41PM (#48100385)
LLMs moved the moments of despair to PR reviews for me. It used to be that you could check on a junior dev occassionally throughout the day to make sure they're on the right track. Now you step away for 2 hours and they're raising a PR of bad code smell spaghetti and moving on to repeat their AI slopfest on the next task.

It's getting hard to keep up with trying to teach new devs what bad code looks like. And I swear sometimes they just copy my PR comments into their AI tool to fix the mistakes without any of the learning.

Re:Software engineering may no longer be a lifetime career by jimbokun on Monday May 11, 2026 @05:44PM (#48101073)
At some point there needs to be an uncomfortable conversation about how if all they’re doing is copy pasting everything they get from you into ChatGPT, you can do it yourself for much much cheaper.
Re:Software engineering may no longer be a lifetime career by trustfundbaby on Monday May 11, 2026 @07:16PM (#48102031)
how? management in most Tech companies are incentivizing them to do just that, so if you bring it up, they'll happily trot over to your manager to complain and then the uncomfortable conversation is you with management about why you're getting in the way of AI uptake by the team.
Re:Software engineering may no longer be a lifetime career by eecc on Monday May 11, 2026 @05:35PM (#48100966)
Don’t allow juniors to use AI. It’s like university exams: no programmable calculators allowed. Review assistants or senior who know what’s going on should though, it does help when used correctly
Re:Software engineering may no longer be a lifetime career by FrankRay78 on Monday May 11, 2026 @05:40PM (#48101024)
Write a damn good automated review agent that runs against their PRs before even looking at them… works well for me!
Re:Software engineering may no longer be a lifetime career by hackeman300 on Monday May 11, 2026 @06:37PM (#48101647)
I've tried this without much luck. In my experience they get too bogged down on surface things and don't have the necessary business requirements/context to understand and find actual bugs.

How have you set yours up that works well for you?

Re:Software engineering may no longer be a lifetime career by marcus_holmes on Monday May 11, 2026 @10:27PM (#48103498)
So create a context document that explains the business context, and add that to the agent.

Take the bad result that you're getting, and pretend it's coming from an enthusiastic junior. What would you tell them to make them do this task better? Add that explanation to the agent (or explain that to the LLM and get it to add that to the agent, I have found this to work as well).

When you create a task for the LLM, get it to create a requirements document that lists all the requirements. Feed that into the review agent so it understands what the code agent was trying to do.

The LLM will do what you tell it to do. It doesn't magically understand what you want it to do. You have to tell it what to do.

Re:Software engineering may no longer be a lifetime career by ncruces on Monday May 11, 2026 @05:52PM (#48101147)
They created other kinds of despair.

A year ago I would've told my boss “can't be done” about my work today. I'd tell him to get me the right person to talk to (our partner, not an alien) who could give me some insight into what the hell I'm supposed to be doing to consume their API. Or to at least explain why it is that this can't be done.

Nowadays, I spent a couple of weeks reverse engineering their terrible ideas. Yeah, it worked. But it's a complete waste of my time, and tokens, energy, chips and RAM. And worst of all, it will lead to a terrible design.

That will work, but will eventually colapse under its own weight, as we use our increased power to increase our sloppiness and take it a little further. Because we can manage it. For now.

Re:Software engineering may no longer be a lifetime career by leptons on Monday May 11, 2026 @07:48PM (#48102324)
LLMs create typos in the code they create all the time. Claude 4.7. Maybe you are using some next-gen super-AI nobody else has? Or you're just lucky.
Re:Software engineering may no longer be a lifetime career by marcus_holmes on Monday May 11, 2026 @10:31PM (#48103523)
So get the LLM to test and fix those typos. Why are you letting it mis-spell things?
Re:Software engineering may no longer be a lifetime career by leptons on Tuesday May 12, 2026 @02:38PM (#48112429)
Maybe you aren't familiar with how AI works. It writes the code for you. Nobody is "letting it mis-spell things". You run the code it wrote, it fails. You look through the code the AI wrote and find the typo it put in there, or give the AI the error for it to fix - but it still created the typo, and that is the main point here. AI often ignores the rest of the document and does what-ever-the-fuck it wants to make you stop prompting it, without any real concern for correctness.
Re:Software engineering may no longer be a lifetime career by marcus_holmes on Tuesday May 12, 2026 @08:14PM (#48116285)
No, that's not how it works.

It writes the code for you. Then it runs the tests. Then it runs the linter. Then it runs the static analysis tool. If any of those fail, then it rewrites the code and runs them all again.

You only look at the code once it has done all of that.

If AI is ignoring the rest of the document and doing whatever it wants then you need to improve your document-writing skills. You can ask it why it did something, that helps discover how to improve. It's a process of refinement and discovery, just like learning how to use any new tool.

Re:Software engineering may no longer be a lifetime career by leptons on Wednesday May 13, 2026 @12:22PM (#48124015)
Maybe you aren't familiar with all the ways AI can be used.

I use AI in two ways. In the way you describe, and also in the text editor as AI autocomplete. It works great until it doesn't. It inserts typos all the fucking time.

Also, don't assume you know it all.

Re:Software engineering may no longer be a lifetime career by suzzer99 on Monday May 11, 2026 @09:45PM (#48103200)
100%. Googling when you don't even know enough to ask the right questions, with 50 tabs open and trying to read down to the 3rd or 4th Stack Overflow answer (which is usually the best for some inexplicable reason), was my least favorite part of development.

I don't miss wasting an hour on a problem in a technology I'm not familiar with, where it's not like a big conceptual thing but something I could clear up in 5 seconds if I just had an expert in the room.

Re:Software engineering may no longer be a lifetime career by pear01 on Monday May 11, 2026 @03:40PM (#48099680)
This is temporary. What is the SKILL.md equivalent going to be in five years? In ten? You don't already see a pattern emerging around solutions to encode that "professional experience" into the tools themselves?

These LLMs can already incorporate our entire cultural corpus yet your "professional experience" is the threshold they won't cross?

Re:Software engineering may no longer be a lifetime career by datsci_est_2015 on Monday May 11, 2026 @04:11PM (#48100031)
The word “incorporate” is doing some very heavy lifting in your assertion. These LLMs already have access to the whole corpus of architectural knowledge and software best practices, and yet they’re unable to reliably implement those best practices. Why not? Why do they often make completely unintuitive decisions, even when repeatedly prompted to ask clarifying questions?
Re:Software engineering may no longer be a lifetime career by pear01 on Monday May 11, 2026 @04:18PM (#48100146)
To be clear by that and "cultural corpus" I meant their skill with natural languages. It is well known for instance that early LLMs were curiously better at composing sentences in English than doing basic math.

Regarding such formal reasoning we have already seen marked improvement in the last year or two alone. The question is how this weighs on your prediction re their capabilities in the next two, five, ten, etc years.

Re:Software engineering may no longer be a lifetime career by datsci_est_2015 on Monday May 11, 2026 @04:49PM (#48100472)
What are the properties of LLMs that have convinced you that there remains emergent complexity (e.g. the “ability” to formally reason) that we have not yet seen?
Re:Software engineering may no longer be a lifetime career by pear01 on Monday May 11, 2026 @05:10PM (#48100730)
There may be gains to be had in such emergence but that is not where I see the gains in the next five years. Those gains will be made by connecting LLMs more robustly with formal reasoning, which computers are already very good at. Continued iteration on connecting these right/left brain faculties could then lead to further emergence down the line.

The present notions of harnesses, structured output or looping in the LLM to some external state or sandbox be it debugger output or embedding into a runtime already show early promising results along these lines. I see no reason to believe these gains will not continue over the next five years.

If you have some theories in the converse in that regard I am all ears.

Re:Software engineering may no longer be a lifetime career by datsci_est_2015 on Monday May 11, 2026 @05:39PM (#48101021)
Extraordinary claims require extraordinary evidence, not the opposite. There’s no current evidence to suggest limitless progress, or even superlinear progress with regards to compute and energy. My guess would be sub linear or even logarithmic progress vs. linear growth in compute and energy, as that’s how most physical systems behave.
Re:Software engineering may no longer be a lifetime career by pear01 on Monday May 11, 2026 @05:52PM (#48101145)
No one said unlimited progress. Let's not revert to straw man claims.

If you think the potential of LLMs is overblown feel free to short the market. I don't pretend to know the future. But if I may, I don't think you are framing the debate in the correct terms. Evidence is an important facet of human affairs. So is risk. Best of luck with your predictions.

Re:Software engineering may no longer be a lifetime career by thinkthatover on Monday May 11, 2026 @07:03PM (#48101922)
I really don't like this framing - it's hard to short a market at the best of times, let alone when governments have a vested interest in tech being too big to fail to compete in the global economic arms race - see Intel's stock in the past few months.

I agree with you both - undoubtedly there are still massive gains to be made with the frontier models we have today with tooling and iteration, yet I do not believe there's sufficient evidence to claim we are rolling towards AG/SI on an exponential curve, without some additional breakthroughs given the jagged edges and data used to train models being fundamentally linear

Re:Software engineering may no longer be a lifetime career by pear01 on Tuesday May 12, 2026 @12:39AM (#48104248)
Just remember you don't need AGI to see massive societal change. Certainly not mass layoffs. AGI is not the bar. By the time we all agree AGI has come the world will have already changed.

You just need AI to be just good enough to win the tradeoff over a human employee. Just take your average office. Then ask yourself if the bar is really that high. AGI strikes me as an extremely nebulous concept. Better to just list everyone at your office and bucket them with a guess of how soon you think AI will replace them. Or weaken their market power. This is what every corporate boss in America is already doing. I'm merely suggesting rather than hope a graph curves in our individual favor we try to act more collectively as a species. Of course, I don't hold my breath.

I also don't find myself compelled by the notion that the danger to humanity is "AGI". The true danger is as it always has been - each other.

Re:Software engineering may no longer be a lifetime career by datsci_est_2015 on Tuesday May 12, 2026 @07:49AM (#48106914)
> Just take your average office. Then ask yourself if the bar is really that high.

How many years away do you think we are from a “concierge” AI that can do the menial tasks handled by most personal assistants / program managers? Booking flights and hotels and coordinating employee availability?

Re:Software engineering may no longer be a lifetime career by datsci_est_2015 on Monday May 11, 2026 @09:21PM (#48103013)
Markets can remain irrational longer than anyone can stay solvent (especially when wealth is as concentrated as it is currently: one doofus can keep an entire industry afloat).

“Unlimited progress” is not a statement on the rate of progress, it’s a statement on the limits of progress. It’s a much weaker claim than you’re framing it as. Your claim very much is that we have not yet reached the limits of LLMs potential. My claim, conversely, is that we’re already reaching diminishing returns, which are being masked by a massive influx of compute and energy. My short: LLMs are not the path to AGI.

Re:Software engineering may no longer be a lifetime career by antonvs on Monday May 11, 2026 @05:03PM (#48100652)
> Why do they often make completely unintuitive decisions

Most likely because you haven't constrained their behavior in your prompt. You're making the assumption that they "understand" that using best practices is what you want. You have to tell them that, and tell them which practices they should use.

Re:Software engineering may no longer be a lifetime career by datsci_est_2015 on Monday May 11, 2026 @05:36PM (#48100978)
They already fail consistently follow very simple and concrete instructions like “Please do not ever mock this object, always properly construct it in your tests”, so I’m not sure how they’re going to adhere to more vague and conceptual architectural paradigms. This is a problem with generative AI in general - image generation has similar limitations.
Re:Software engineering may no longer be a lifetime career by antihipocrat on Monday May 11, 2026 @06:01PM (#48101240)
Senior developers know what behavior to constrain.

If incorrect LLM output is a prompt issue then demand for experienced developers will remain, and demand may actually increase as time passes.

Re:Software engineering may no longer be a lifetime career by ecocentrik on Monday May 11, 2026 @03:46PM (#48099764)
The capacity of the person prompting it to understand is the threshold they won't cross. They can squeeze the gap as much as possible by dumbing down answers or slowly ramping up information complexity but there is a limit to comprehension.
Re:Software engineering may no longer be a lifetime career by pear01 on Monday May 11, 2026 @03:57PM (#48099869)
This is an interesting answer for questions about human agency and accountability/personhood questions but I don't see how it leads to increased confidence in the role of human as SWE.

If LLMs get good enough, one might be tempted to ask so what if most humans can't understand the output? Human civilization has by and large been a constant exercise in us collectively accomplishing more and more while individually comprehending less and less.

Our ancestors likely understood more about hunting live game or murdering each other than we do. Most of us do not consider that a great loss. Most of us living in the modern world depend on things we don't fully comprehend. I'm just not sure how this would lead to being reassured re the human as SWE.

Re:Software engineering may no longer be a lifetime career by npodbielski on Monday May 11, 2026 @04:32PM (#48100285)
Do you really want to live in a world when nobody understand software that manages nuclear power plant? Or medical devices? Or financial software? Or radio transceivers firmware? Even something so boring like databases not understood could lead to disastrous effects if this would be the government database for managing people IDS. Hmm even if this would be working fine for years what would happen if bad actor would influence models to generate code if security issues? If nobody can comprehend the output how anybody would be able to think about the danger? This is even more grim then this https://www.citriniresearch.com/p/2028gic
Re:Software engineering may no longer be a lifetime career by pear01 on Monday May 11, 2026 @04:42PM (#48100403)
We live in a world with nuclear weapons. Somehow we all cope and get up every morning. I think you are missing the point - the world is already grim. It always has been. What about human affairs say in the last century alone makes you think human oversight is some panacea? The impetus for civilization was not some innate desire for financial systems or medicine. It was not having other humans murder you. The Leviathan is already here.

The article you shared has little to do with this. Questions of how to divide up gains technology creates are a separate question from that of the technology itself. Tbh I found what you shared so boring I could barely finish it. I already in this thread made an exhortation to support politicans who commit to erasing inequality. The idea that LLMs can only exist with inequality is nonsensical. The only thing grim about what you shared is the lack of political imagination. It's boring.

Re:Software engineering may no longer be a lifetime career by jimbokun on Monday May 11, 2026 @05:49PM (#48101121)
At least we have people who understand the technology underlying nuclear weapons!
Re:Software engineering may no longer be a lifetime career by esafak on Monday May 11, 2026 @05:26PM (#48100894)
Maybe the tables will turn and people will ask, do you really want to live in a world where things aren't designed by machines (smarter than us)?
Re:Software engineering may no longer be a lifetime career by ecocentrik on Monday May 11, 2026 @04:45PM (#48100431)
We don't need as many hunters because we've domesticated sources of meat. We still need ranchers, butchers... an entire supply chain to get meat to consumers. We didn't remove humans from the loop, we just created specializations.

Software specialization might look very different in 10 years but I doubt that technically specialized humans will be completely removed from their professions. We might not be carrying bows and arrows anymore but we will be carrying the equivalent of a rope and a Stetson.

Re:Software engineering may no longer be a lifetime career by pear01 on Monday May 11, 2026 @05:23PM (#48100861)
Ranchers, butchers... and factory farms. Most meat Americans consume have had very little interaction with a person until they are being devoured on the plate.

I appreciate your points. I agree with you that not all "technically specialized humans will be completely removed" but let's not pretend the comparison is going from a caveman with a spear to a cowboy with a lasso. If you concede it is likely to be very different at some point calling it SWE is no longer useful.

I think SWEs would be better off realizing they have enjoyed a relatively extreme level of privilege, and rather than trying to hold onto it, use what time they still have to advocate for a more egalitarian society, even if that means giving up some of their gains. Otherwise speaking of farming, the mass layoffs to come when software has been disrupting blue collar jobs for decades will really be a chickens coming home to roost moment.

Re:Software engineering may no longer be a lifetime career by ecocentrik on Monday May 11, 2026 @06:47PM (#48101755)
Now you're arguing against your own analogy? Hunter was ubiquitous position in human society prior to the domestication of animals. 50% of the workforce in hunter-gather societies. Today, 12 millennia after the domestication of wildlife, that number is down to 9-14% of the global workforce dedicated to the production, distribution, processing, sales of meat (not including cooked food) according to opus.

Considering that only 1% of the US workforce was a software engineer I expect similar workforce optimization to occur in software engineering specializations over the next 12,000 years. /s But seriously, it's never going to zero.

Re:Software engineering may no longer be a lifetime career by pear01 on Tuesday May 12, 2026 @12:25AM (#48104179)
No one said it's going to zero. It doesn't have to go to zero for lives to change. Would you rather be a cowboy or a factory farmer? The latter are some of the least desirable jobs in the entire world. The fact that millions of people still do them isn't the point in your column you think it is.
Re:Software engineering may no longer be a lifetime career by jimbokun on Monday May 11, 2026 @05:47PM (#48101109)
The software specialists may be replaced entirely by subject matter experts.

No need for specialized commercial software, if everyone can just explain to the computer what they want in English.

Re:Software engineering may no longer be a lifetime career by sleight42 on Monday May 11, 2026 @03:38PM (#48099673)
This is far more true for junior and perhaps mid-career engineers, unless you're working in an extremely well-defined problem space (* see below).

When working as a SWE, the longer I did it (~30 years) more of my time was spent understanding the problem, the edge cases, how to handle the edge cases, how to do all of it affordable, on time, and within budget.

That's engineering.

What you're describing is "writing code". That's lower value than "solving the problem".

I imagine a response, "But agile development, etc."

Yep. Part of solving the often sometimes involves creating prototypes to determine the essential viability of the solution. But that's only part of it. Which prototypes do you write? How much time do you allocate to same before accepting it's a dead end (at least for now) and punting on it?

That's engineering.

Me probably coming across as a dick today? Well, I was diagnosed autistic a year ago, and I'm on extended sabbatical/unemployment (3 years now) due to autistic burnout. And masking is part of how I got the burnout.**

* Why would someone be paying for that when there is likely someone else already doing it? Unless you're the rare person who hopes to "disrupt" the competition).

** has me begging the question of why I write here at all. SMH. Why do I do what I do? No idea sometimes.

Re:Software engineering may no longer be a lifetime career by cduzz on Monday May 11, 2026 @04:20PM (#48100162)
I'm going to mix my metaphors a bit here...

There's the saying "Any idiot can build a bridge; it takes an engineer to build a bridge that barely stands."

To put this another way, any idiotic LLM can write code. It takes a person with domain experience to understand what code to write, rewrite, or not write.

I've seen lots of organizations hollow out their internal competence in favor of outsourcing the skills. LLMs are the ultimate expression of that. There are people who say "you need to have people in your organization who understand how things work because they're the ones who solve problems!" and there are other people who say "focus on your core competencies! These problems you're worried about aren't your core competencies, so get rid of those experts, they're expensive and annoying; we can just sign a contract with an organization that'll know things for us."

At some point we all will identify exactly how much "seed corn" you need for the next season. We'll figure that out because we're starving, but at least we'll all know.

Re:Software engineering may no longer be a lifetime career by dijksterhuis on Monday May 11, 2026 @05:24PM (#48100869)
you've definitely been doing this longer than i have, but our outlook and recent experiences sound very similar. also been diagnosed recently, also on similar extended sabbatical/unemployment, also come across as a dick, also trying to mask less because burn out.

got an email address in my profile if you'd be interested in talking at some point about something, or even talking about nothing in particular. (i don't normally do this sort of HN networking stuff, i find it super cringe. but there we go).

Re:Software engineering may no longer be a lifetime career by bborud on Monday May 11, 2026 @02:04PM (#48098420)
Are you, perchance, assuming that since you spend most of your time struggling with actual code, this is so for everyone else?

Or are you saying that I'm lying. That I am secretly hammering away at my keyboard while pretending not to?

No, writing code hasn't been how I spend most of my time for many decades now.

Re:Software engineering may no longer be a lifetime career by therealdrag0 on Monday May 11, 2026 @02:06PM (#48098452)
Are you a staff level engineer that has dozens of other engineers banging away at code projects you help define?
Re:Software engineering may no longer be a lifetime career by eska on Monday May 11, 2026 @02:14PM (#48098569)
Try to write a design doc before you implement something (which people find they need to do for LLMs to work at all anyway). You’ll find that you spend much less time actually writing code.

Write proper API documentation laying out the assumptions and intent, generate some good API docs, write a design and architecture document (which people find they need for LLMs to work at all anyway). You’ll find that you spend a lot less time reading code.

Re:Software engineering may no longer be a lifetime career by dkersten on Monday May 11, 2026 @02:25PM (#48098727)
> which people find they need to do for LLMs to work at all anyway

Everything we have to do for AI to function well, would help humans to function better too.

If you take the things for AI, but do them for humans instead, that human will easily 2x or more, and someone will actually understand the code that gets written.

Re:Software engineering may no longer be a lifetime career by overfeed on Monday May 11, 2026 @04:01PM (#48099911)
> If you take the things for AI, but do then for humans instead, that human will easily 2x or more, and someone will actually understand the code that gets written

This only works on high-trust teams and organizations. A lot of AI productivity gains are from SWE putting the extra effort because the results will be attributed to them. Being a force-multiplier for others isn't always recognized, instead, your perfomance will likely judged solely on the metrics directly attributed to you. I learned this lesson the hard way by being idealistic, and overestimating the level of trust that had been built after joining a new team. Companies pay lip service to software quality, no one gives a shit if your code has the lowest SEV rates.

Re:Software engineering may no longer be a lifetime career by dkersten on Tuesday May 12, 2026 @03:07AM (#48105154)
Ah… that’s a reasonable point. Yes, the difference between a high-trust team and what you described is night and day. I suppose for those situations there’s a much bigger incentive to just throw AI at it, which explains why the big corporates love AI.
Re:Software engineering may no longer be a lifetime career by bborud on Monday May 11, 2026 @02:16PM (#48098587)
It has varied over the years but it isn't actually relevant since I am talking about when I write software.

Writing code just isn't what takes time.

Re:Software engineering may no longer be a lifetime career by QuercusMax on Monday May 11, 2026 @02:22PM (#48098679)
Getting the code into a state where it actually does what you want takes time - but a lot of that is research, testing, experimentation, documentation, etc. Those can be faster with AI assistance but you still need to bang on it enough to make sure it works right.
Re:Software engineering may no longer be a lifetime career by kakacik on Monday May 11, 2026 @03:07PM (#48099289)
I am not, yet actual coding is miniscule part of workflow. The rest is cca un-automable by any llm - politics, meetings, discussions, brainstorming, organizing testing teams, stakeholders and so on.

This is how big corporations look like, not some SV startups.

Re:Software engineering may no longer be a lifetime career by munksbeer on Tuesday May 12, 2026 @03:16PM (#48113060)
I agree. And that stuff is soul destroying. I have done it, and right now I work in a place a little smaller, but we get so much done without all the cruft. And we get it done better. I spend much more time writing code now (*) than at the big corps, and we do a much better job because we can iterate.

(*) Well, now claude spends a lot of time writing code, I spend a lot of time designing and steering it. Claude can write remarkably sophisticated code with the correct steering.*

Re:Software engineering may no longer be a lifetime career by prmph on Tuesday May 12, 2026 @06:03AM (#48106189)
No, no actually capable engineer should be just banging away at code. This is one way to know the level of an engineer.

Less capable engineers think in terms of implementing runtime execution and solving runtime errors.

More capable engineers think in terms of designing the most effective architecture and abstractions for maintainability, performance, and robustness.

I have a project I am working on, It has not compiled in months, but that's ok, since the real work, for me, is in the architectural design.

Yes, getting it to actually run takes some time and effort, but for me that is almost mechanical now.

Re:Software engineering may no longer be a lifetime career by pear01 on Monday May 11, 2026 @03:25PM (#48099527)
Let's also not forget a lot of the market edge of SWEs comes in knowing how to navigate these parts. The fact you needed to be reasonably fluent in a language was already a barrier to entry which meant in better times new grads could earn six figures at their first job just for putting in that effort.

Maybe you will still be needed. That is one question. How well you will be paid and treated when the barrier to entry is now "I can think" is another. As the parent indicates, most people doing software are not doing things akin to pure math. I don't think most SWEs want that lifestyle anyway.

It's ok. You shouldn't fight the coming change. Instead use the time we still have to fight for more equal outcomes (vote for politicians that support UBI, Medicare for all). The longer you delude yourself that you are uniquely needed in an increasingly mechanized world the worse all our outcomes will be.

Re:Software engineering may no longer be a lifetime career by arandomhuman on Monday May 11, 2026 @04:03PM (#48099941)
The barrier to entry to generating code may be "I can think", but the barrier to entry for solving hard, distributed/multi-faceted engineering problems still remains quite high - agents can't really do this still to a decent level of efficacy reliably.

The progress models have made in the last 5 years aren't convincing me they'll bridge that gap too soon, although I can see how some people are convinced by how decent agentic harnesses make things. I know it's really easy to get very hyped with the current state of the technology, but try to have a bit of skepticism.

Re:Software engineering may no longer be a lifetime career by logicchains on Monday May 11, 2026 @03:04PM (#48099261)
>OP's formulation makes SWE sound like a purely noble enterprise like mathematics. It's more like an oil rig worker banging on pieces of metal with large hammers to get the drill string put together.

Those two formulations represent different developers' approaches to the same task. The former being developers who are much better at planning than the latter.

Re:Software engineering may no longer be a lifetime career by 01100011 on Monday May 11, 2026 @04:50PM (#48100479)
Your answer reminds me that my biggest gripe with this site and programmer forums in general is the lack of awareness of the breadth and scale of software development. I'm curious what you work on, because it doesn't sound anything like what I work on.

> Most of the time is spent coding which encompasses typing, retyping, and retyping again. It also includes banging your head against the wall while trying to get one of your rewrites to work against and under-documented API.

I don't think I've experienced this to a large degree. Maybe early in my career. Most of my time now is spent formulating a solution, and time spent coding is mostly spent trying to compose my changes with the existing code in a way that is performant, reliable and meets the specifications.

Re:Software engineering may no longer be a lifetime career by RajT88 on Monday May 11, 2026 @07:15PM (#48102027)
> under-documented API

One wonders why AI hasn't replaced all those non-existent documentation writers yet.

Therein lies a clue to what the future holds.

Re:Software engineering may no longer be a lifetime career by AussieWog93 on Monday May 11, 2026 @07:35PM (#48102226)
This was my experience as a junior back in 2019.

The actual problem solving was trivial but I would spend days trying to work my way around some Qt work or guess the magic Cmake incantation.

Re:Software engineering may no longer be a lifetime career by Sh0000reZ on Monday May 11, 2026 @07:38PM (#48102253)
Lol @ sitting in a cushy office chair is like working on an oil rig, one of the deadliest jobs out there. Insanity.

You tried to make it sound like a far more noble and risky thing than it is.