Top
Best
New

Posted by napolux 1/11/2026

The next two years of software engineering(addyosmani.com)
328 points | 383 commentspage 4
FrustratedMonky 1/12/2026|
Maybe a harsh criticism. The article seemed to be all over the place, maybe because the subject is also all over the place. I agree with everything, its just that it seemed like the same story we've been in for awhile.

Wasn't the main take away generally "study everything even more than you were, and talk/network to everybody even more than you were, and hold on. Work more more more"

pier25 1/13/2026||
Do companies hire less because of AI or try to rely more on AI because they can’t afford to hire?

Tech layoffs have been happening even before LLMs.

kasane_teto 1/12/2026||
Ah, time to drop out and shoot myself in the woods
Havoc 1/12/2026||
One of the better analysis of this question I think.

On the optimistic take side - I suspect it might end up being true that software might be infused into more niches but not sure it follows that this helps on the jobs market side. Or put different demand for software and SWE might decouple somewhat for much of that additional software demand.

slfnflctd 1/12/2026|
I'm mostly convinced at this point that the jobs market will only be affected temporarily.

This is really just another form of automation, speeding things up. We can now make more customized software more quickly and cheaply. The market is already realizing that fact, and demand for more performant, bespoke software at lower costs/prices is increasing.

Those who are good at understanding the primary areas of concern in software design generally, and who can communicate well, will continue to be very much in demand.

Havoc 1/12/2026||
I‘m leaning more towards significant job impact.

It’s hard to tell though not just because it’s inherently uncertain where this goes but also because those closest to it are also the least likely to view it objectively.

So near impossible to find someone clued up but also not invested in a specific outcome

gassi 1/12/2026||
> Addy Osmani is a Software Engineer at Google working on Google Cloud and Gemini

Ah, there it is.

mikemarsh 1/12/2026||
Yep, it never fails. Here's another prediction for "The next two years of software engineering"; AI vendors will start to utilize their senior devs' personal domains to write their advertising pieces to attempt to mitigate scrutiny when such things are posted to social media.
falloutx 1/12/2026|||
Ahhhh, this is like that guy who works at Claude Code and runs 100 agents at the same time to replace 100 juniors. Everyone is convinced he will be the last software engineer on earth.
lesser-shadow 1/12/2026||
[dead]
tommica 1/12/2026||
One thing that fucks with juniors is the expecration of paying for subscriptions for AI models. If you need to know how the AI tools work, you need to learn them with your own money.

Not everyone can afford it, and then we are at the point of changing the field that was so proud about just needing a computer and access to internet to teach oneself into a subscription service.

boulos 1/12/2026||
You can get by pretty well with the ~$20/month plans for either Claude or Gemini. You don't need to be doing the $200/month ones just to get a sense of how they work.
tommica 1/12/2026||
Again, not everyone can afford it, and it becomes a hurdle. Computers are acquirable, but 20$ extra a month might not be.

And yes, that plan can get you started, but when I tested it, I managed to get 1 task done, before having to wait 4 hours.

falloutx 1/12/2026|||
This is why opencode is giving free access to one or two models, unlimited access.
ares623 1/12/2026||
If the AI gets so good then they shouldn’t need to pre-learn.
PraddyChippzz 1/12/2026||
The points mentioned in the article, regarding the things to focus on, is spot on.
dhruv3006 1/12/2026||
I recently started as a developer advocate - I have similar opinions to the author - junior devs have a hard time getting hired and flipping to something like devrel makes a lot of sense.
tom_m 1/13/2026||
I don't know, we hired a junior developer and are about to hire another. Not sure it collapsed. I just think it's really hard to get a job across the board right now.
ahmetomer 1/11/2026|
> Junior developers: Make yourself AI-proficient and versatile. Demonstrate that one junior plus AI can match a small team’s output. Use AI coding agents (Cursor/Antigravity/Claude Code/Gemini CLI) to build bigger features, but understand and explain every line if not most. Focus on skills AI can’t easily replace: communication, problem decomposition, domain knowledge. Look at adjacent roles (QA, DevRel, data analytics) as entry points. Build a portfolio, especially projects integrating AI APIs. Consider apprenticeships, internships, contracting, or open source. Don’t be “just another new grad who needs training”; be an immediately useful engineer who learns quickly.

If I were starting out today, this is basically the only advice I would listen to. There will indeed be a vacuum in the next few years because of the drastic drop in junior hiring today.

ares623 1/12/2026||
What. That’s written in a way that’s like “men writing women”. Not putting themselves in the shoes of a junior who has no context or almost no opportunities.
falloutx 1/12/2026|||
And you think juniors aren't doing this? At this point everyone in the market does more Vibe coding than those who are not in the market. Market is saturated most because Execs cutting jobs not because juniors are not good.
Anamon 1/13/2026||
> be an immediately useful engineer who learns quickly

Then also nothing has really changed. This was, verbatim, the advice everybody was giving when I was a grad student almost 20 years ago.

Back then, the conclusion was to learn the frameworks du jour, even if it was unfulfilling plumbing and the knowledge had a half-life of a few weeks. You needed it to get hired, but you made your career because of all the solid theory you learned and the adaptability that knowing it gave you.

Now, the conclusion is to learn how to tickle the models du jour in the right way, even though it's intellectually braindead, unaspiring work and knowledge with a half-life of a few days. It's still the theoretical foundation that will actually make the junior become a valuable engineer.

The more I read between the lines of AI evangelists' posts like this, the more I'm convinced that expectations will return to grounded reality soon. They are new tools to help the engineer. They enable new workflows and maybe can even allow a two-digit percentage increase in speed while upholding quality. But they're in no way a revolution that will make possible "10× engineers" or considerably replace engineering positions beyond the "it doesn't really matter" area of PoCs, prototypes, one-offs, cookie-cutter solutions, etc.

More comments...