It's like that meme from about a decade back about the millionaire saying that the only reason millennials can't afford houses is that they eat too many avocados. That advice makes sense in a long-gone era where houses are cheap and avocados are expensive, but in the 21st century the price of personal avocado consumption would never add up to a house in a reasonable amount of time no matter how excessive your avocado lifestyle may be. jedbergh is going to be an "avocado guy" from now on (again not that I actually know anything about him).
What is falling away is that we just won't need as many SWEs as we used to. The way to make sure you don't "fall off the ladder" is to make sure you're the best at the new way of doing things.
It doesn't matter how good you are at anything when you can't even get a reply. The ladder is gone. Combined with the war on the middle class and am looking at a retirement in poverty. Even social security will be empty by the time available.
Sorry, I just checked and I don't see anything from you. Where did you ask? I try to respond to everything I get, but sometimes gmail doesn't surface random messages.
I can see this going a few different ways. We could be approaching a future where the machines can drive themselves and the computer goes from being a tool to a partner (ie Data from Star Trek). Or maybe we're approaching the future where computers still require humans to tell them what to do but they're good enough at figuring things out that nobody even needs to understand how a computer works to build the next enterprise-grade large-scale thingamabob.
The future you describe where software engineers still exist but they've carved out a niche managing AI software factories only makes sense if we've just reached the end-state of generative AI and there will only be incremental improvements from here on out. Otherwise I don't think you can safely assume that the AI software factory actually needs anybody with an advanced skillset to tell it what to do.
Success in a prior time does not guarantee success in the present or future as too many variables are different
Demographics have shifted wildly and most users are not a soft spoken grama needing help setting up pop3 in Outlook Express
Look around you; everyone uses their phone at whatever level of expertise they need now
Goodhart's Law has come for how we used to measure need and todos in tech. We hit the top of the S-curve relevant to this form of computing devices and there is nowhere else to go with it
I would understand this comment if I was telling you how to live frugally because it's not my lived experience. But in this case, it is my lived experience. I literally work at a job where I have to build a software factory to be successful.
Perhaps. But I work right now, and I actually care about people other than myself. I would like to see the industry that made me successful keep making others successful.
We'll have to wait a month or two I suppose to find out if you're right, but I think all companies will be moving to the model of software factories. And It's not something I thought of recently -- I've been building a software factory with AI for a year now, and working with others who are building entire businesses on it.
And FWIW, pretty much every tech company is now moving towards the same model.
This is my first reading about your work but I like your attitude. Databricks is also a good service.
From what I am seeing, those who embrace AI are embracing the 'computer' from the 80's. The landscape and reality is still being defined.
To the AI haters and doomers I say buy the largest house with cash you can to enable your retirement. The stress that people experience is the thought of their crushing debt or obligations that can be met with a 90% reduction in spend. Of course, that requires a lifestyle change that most are unwilling to make.
I don't really see a future where human labour at all can still be competitive beyond like 2050 in any field. Anyone who's ridden in a Tesla in FSD knows transport jobs are defacto over, the tech works and it will be deployed en masse sooner or later. Humans don't scale and we haven't meaningfully mentally improved in 100k years, we're limited to 20W of compute, take 20+ years to train and go EoL in 40 after that. It's inevitable that we'll be outclassed and it only needs to happen once. Once a model exists that is slightly better at any arbitrary task, it only gets cheaper over time and it can be used forever.
large groups of people dont have good taste. Its always going to be reversion to the mean. which is just mediocre software
I assume the premise of a software factory is that it can churn out any software idea you have. You won't need to build a new distinct factory for each new distinct piece of software you dream up. Otherwise it wouldn't be called building a software factory, it would just be called building software.
So if somebody gets this right (this remains to be seen, the various Gas Towns of the world have not proven their value), won't one good software factory be enough for everyone to download and use? Wouldn't we all then be done with the labor of making both software and software factories?
For example, I could clearly see having a "Static web page with HTML and CSS only software factory" that just churned out that kind of software. Or a "Postgresql optimized SQL" software factory. And so on.
> end up with a factory factory
java nightmare ensues...every company is making a totally different product so its hard to see how every company is its own 'software factory' outside of such components (which they were already doing even before llms)
And while many companies may have differences, there are certain things most companies need, like a marketing website.
Unless we organize to prevent it, technology will continue be commoditized like all other technology into the hands of a few players.
And especially with AI it’s going to look more and more like nuclear or biological technology and that’s why you see so much push for regulatory capture.
Literally all I do is spend my time trying to figure out how to prevent this, and still make progress towards AGI for everyone, but it doesn’t seem like people care
Everyone just wants their bag everything else be damned, and that’s what we’re seeing
See web dev jobs tanking. Backend is next.
Backend dev opinions/arbitrary strings are being compressed out of the stack.
Devs that don't understand hardware development are naive about the endgame; black boxes that boot to a Google Opal like GUI.
Boot to Blender-like/WYSIWG environment loaded from a model itself. All the context we put in files added as vectors on the presentation layer.
Users will conjure a word processor or email UI and then a video game.
Network gear will boot a model to handle the specific job the model was trained on. That's what all the Stargate stuff is about but obfuscated behind marketing to hide implementation goals details from knowledgeable labor to avoid public scrutiny. Vague scrutiny without concrete proof is fine but if we could point to the details too they'd be naked.
50 million devs among 8 billion that do not want a subscription service to an expert when they have no such leverage over the expert themselves.
This isn't empty speculation. Hardware industry executives are responding to social pressure at scale.
America was able to leverage its clout to empower IT to pretend it's more than just math relative to memory and display matrices but America no longer has the global clout to assure that. To Chinese engineers it's just math.
American software devs were engaged in sophistry and social moat building. Ya got disrupted by the world. Believed they would ignore their eyes for the rhetoric and hype forever; rather Orwellian really.
The work of software engineers has enabled a (temporary?) profession of mostly busy-hands sort of work to thrive. It will now move onto enabling a different sort of work.
This is multi-generational change happening in a decade. This is disruption across nearly all industries. We can't just waive that away. There are going to be consequences.
£300 is equiv to £485 today too
Similar Loakes go for ~£320 and Cheaneys ~£500 today! https://herringshoes.co.uk/collections/oxford-shoes?filter.p...
We have to balance "a lot of people can get the product" with "product is high quality" somehow.
Eventually we just accept the new status quo, and the QOL hit that comes with it.
Anyone who hasn't FIRE'd yet should aggressively be saving as much as possible before shit hits the fan.
Good luck everyone! It's going to get ugly.
(And I'm getting lots of job offers. But I'm in Singapore, and that's presumably not where you are.)
I'm 40 now. Not sure if that counts as older.
"if its used correctly and broadly"
It's not enough to just have a claude code subscription for every engineer.
The powerband of AI comes through automation, integration, and tooling. When literally everything is touched by AI, and when most tasks get passed through AI before seeing a human, only then are you actually at an AI-first shop.
Only then will you actually realize how little you do in this AI-first world.
"You are holding it wrong."
Now it seems like it's the sunset of this way of making a living. I think people who manage to move up the food chain a bit will succeed but its hard to advise any junior in the industry exactly what that looks like.
You got 50 years, but many people haven't. There are so many people out there in the prime of their careers right now, I genuinely worry about them and what this does for their livelihood.
If I could pick an age for this all to happen, it would be when I was 16, just starting to get into computers. I think I would enjoy the hell out of the new world, getting in on the ground floor at the very start of my journey. But my 2nd pick would be my current age, at the tail end of my career. I get to see this crazy transformation, but I've already reaped most of the rewards of everything I learned that is potentially becoming quickly obsolete.
I really don't envy those mid-career, who have put tons of work into their craft but have yet to reap the majority of the rewards (which tend to be stacked later in career rather than evenly spread out.)
You've worked hard and build a knowledge-base that was extremely lucrative; That's becoming less and less true. The "democratization" of software is a great thing for people who wanted to get into it, but found it too difficult. It's a horrible thing for those who made a living on it being difficult.
And I'm not even advocating that we should halt progress. This is how humanity has always evolved technology. Jobs exist where technology can't replace them, until it does. Software had a good run, I just wish it'd been longer.
Nearly everything will (eventually) be impacted.
Therapists? People are using LLMs for “free” help.
Physical trainers? Just upload a video of your workout for tuning advice and other exercises you can focus on.
Appliance/vehicle repair? Just DIY it with an LLM.
Teachers? Just teach yourself with and LLM.
I could go on.
To be clear, I’m not saying LLMs are better at this. But just saying LLMs are impacting nearly every field.
More workers competing means lower pay. Less good paying jobs means less customers. Less customers means less jobs. This is an over simplification, but is one possible future.
I'd be happier if my prediction turns out wrong.
But never mind that. Get money or die. Every rat for herself.
Nothing makes sense or is computable when human labor/knowledge has little to no value. It's a bit like an economic event horizon
Actually makes everything a lot simpler, economically.
Economics is the study of how to equitably distribute scarce resources. When everyone's contributions are equally meaningless (because hey, we made this do-everything bot that will do your job, no matter how much you were worth in the before-time) then the whole convoluted, often inequitable distribution scheme is paved over with the brutal 'your share = [resources] / [number of people]' equation.
Ownership is a social construct, backed by the rule of law. If we rapidly take away the ability for the masses to be able to afford to own things, there isn't any magic preventing them from deciding to not honor that particular construct anymore.
The bigger question is, if that does come to pass, will the AI overlords still have enough power to enforce their ownership claims the old fashioned way -- with violence?
I'm afraid this is going to get very ugly.
200 years ago, in the US, 85% of the labor force was employed in the farming industry. 100 years ago, it was 40%, and now it is 1.5%, almost a rounding error.
We are far better fed, spend almost none of our time as a society farming compared to what used to be almost all of our time. There are few people left who have any serious knowledge of how to grow food.
Yes, the period of transition will be faster. And the transition will happen to a different class of workers. And, yes, our current food,in many ways, is mostly crap.
The future will be quite different
The real danger for teachers is society deciding people don’t need to be educated. Although that would be a problem for all of us actually.
Sure, in THEORY we can do all these things, but I suspect this fear is somewhat borne out of the same error that mashes us estimate a task will take 6 hours and then it takes a week.
We systematically underestimate the human effort needed. How many non-technical, non-interested people are going to be looking up DIY for fixing their car, buying the needed equipment, developing the skill, etc, really?
While they’re doing that, they’ll somehow also have time to produce their own movies, write their own indie games, etc, etc.
Fast food is available; people still go to restaurants. I can sketch on a piece of paper, but I still buy art. It’s technically not difficult to build a chair, but I still buy furniture, etc.
It’s going to have a massive impact for sure, but we have to temper our expectations and ground them in real, practical limits.
Definitely some interesting years ahead. Fingers crossed.
Done right, that accreditation could be objectively superior to brand names like Harvard, etc.
And the results are poor because the LLM does not have a face and is not reading your facial expressions or hearing the tone of your voice. We communicate with more than just the words we speak.
> Physical trainers? Just upload a video of your workout
...lol
> Appliance/vehicle repair? Just DIY it with an LLM.
"Officer you can't arrest me and impound my car, I did what the LLM told me to do. It's not my fault that a wheel fell off and my exhaust is an eerie green color!"
> Teachers? Just teach yourself with an LLM.
See above about therapy, there is more to teaching than spitting out words.
> I could go on.
You could, but at what point will you get to the few lines of work that are genuinely going to disappear because of this technology? Taxi drivers are the most obvious, and least discussed, example -- self driving cars will eliminate that entire profession over the next few decades.
I don't disagree. But I think people will still use it. We've seen how people Googled stuff to get help in this area, and it's 100x easier with LLMs.
>> Physical trainers?
> ... lol
I disagree here. I think LLMs are decent at getting someone dumb to working out, like me, from zero to establishing a decent workout plan, and making adjustments as you go, if you give it enough context on your health, and how things are working for you.
Again, I'm not saying LLMs are better at it, but I think it's arguable that people will figure out that they can use an LLM to get started pretty easily, where they used to go to physical trainers.
> "Officer you can't arrest me and impound my car, I did what the LLM told me to do. It's not my fault that a wheel fell off and my exhaust is an eerie green color!"
I was already doing a lot of my own home/vehicle work via YouTube. Now I almost never taking my vehicle into the shop (for what I think are relatively small repairs that aren't safety hazards, like fan repairs, electronics, etc.).
Additionally, I now upload repair estimates to an LLM, and have it push back on things that I can either do myself, or do somewhere else and save a lot. And this has, indeed, kept me from spending as much for vehicle repairs (cutting into their margins).
Similarly, I've uploaded pics/videos of appliances bugging out on me, and have been able to fix many things myself. I used to already do this to an extent with YouTube, but would still have to figure a lot of things out myself. Being able to upload pics/videos changes things quite a bit.
>> Teachers?
> See above about therapy, there is more to teaching than spitting out words.
Again, agree mostly on this one. But the value of higher education has already been in question for a while, and I think LLMs are only pushing this further.
I don't think teachers/professors will get replaced (anytime soon), but I have kids and know parents of kids that are using LLMs to help them in ways that they used to rely on teachers for.
> You could, but at what point will you get to the few lines of work that are genuinely going to disappear because of this technology?
I'm not necessarily talking about full replacement. Agree that this is very possible/likely with taxi drivers. And I do think some fields will also get replaced, some that we may not even consider now (would we have thought 15 years ago that taxi drivers would get replaced in our lifetime?).
But my point is that LLMs are going to, at the very least, have an impact on many non-digital fields.
The results are more 5* reviews than 1*: https://apps.apple.com/us/app/feeling-great/id6450066153
I think this is a very good template for what sort of skills will survive the LLM-apocalypse and what won't. LLMs are the great homogenizer. Any type of knowledge work where there is a broadly-accepted set of best practices for how to do it is gonna get outsourced to an AI.
But AI is terrible at doing anything unique, personalized, and based on your own desires, because it doesn't have your desires. It's building on a corpus of shared knowledge, but there is a large set of knowledge that is unshared, and it can't do anything for that. A large portion of business, for example, is secrets and lies, and an LLM isn't going to be able to help you much with that. At its best it can set up the frameworks and tools to help you keep secrets and tell lies.
And then a large portion of life is personal preferences, the things that make you unique and distinct from every other human, and an LLM can't help you with that either. There is a reason I don't have a nanny raise my kids, even though we could afford it. If I did that, it would be the nanny raising my kids, which defeats a lot of the point of having kids in the first place. LLMs have the same problem.
I keep trying to nudge them to be relevant with specific examples of a few shows I had watched that were very popular at the time but now considered "old/boring/not remastered" so don't make it into the Best X Shows of XXs lists that emphasize modern tastes. But the recommendations were either the same things I already knew about, or were just wrong/irrelevant for various reasons.
Recently I stumbled onto a Reddit post from years ago with a similar request to mine, and both the question itself and top answers were a goldmine of suggestions that were never recommended and I hadn't heard of. I knew within seconds of looking at the IMDB that they would be exactly what I wanted, so it's not like the AI recs are failing just because of idiosyncratic taste. They just don't seem to search from a deep enough info source, have been RLed into conformity, or some other disconnect between intent and execution.
Or — more disturbingly — what if LLMs lock us into our current state of development forever? This is all we will ever be; nothing will fundamentally change from here on out.
Cars are too expensive to not repair, but the complexity of car repair is way too high. Even with an incredibly specific and accurate video, even one made lovingly by a knowledgeable mechanic, most repairs are beyond most people’s physical skills.
I do mostly agree with your thesis, still. Being closer to education than many other fields, though, I remain unconvinced that AI will handle children well.
College, on the other hand? For many reasons, colleges should be an existential crisis right now. Nothing about college makes sense from cost to how AI-cheating changes things, to job prospects for most majors.
Good luck replacing elementary / high school teachers with LLM's. Their job is about so much more than just teaching.
My wife has a deep expertise in modern therapy* and I saw her use ChatGPT. The difference is between "I want to fetch better products" vs "modify this index to use embeddings with model XXX"
*people's mental model of therapy comes from the movies, books or TV shows. Modern therapy doesn't look like an episode of Sopranos
Is this the limited of UI/UX(like no visual input to the model), or it's flawed in the core ?
The first one can be fixed.
What is the common thread?
These roles depend on some combination of physical skill, human connection, trust, judgment and accountability, and such jobs are out of reach of AI.
Arguably, software has times that require physical presence, human connection, trust, judgment, and accountability.
Depends on what the software does and it is application.
If its a tiny video game, journaling app or camera app that requires little human interaction: Then it isn't important.
If it is infrastructure-level, critical and time-sensitive and deals with highly regulatory industries such as finance, crypto, healthcare, legal, manufacturing and has a chance of risk to the human then that software will continue to be used and pay will remain high.
Then they will be able to do more and more, and 1 nurse will be able to do the job of 4-5 2020 nurses.
Until that nurse is a dude from Mexico [where im from/based] giving instructions to all the robots.
There are some professions where human touch is in demand (this is not about capability, but about user experience in sense of human interface)
The same way I [as an Xenial] prefer to use the self-checkout in the supermarket to avoid contact with the cashier lady or the person that bags items [here in Mex].
I imagine when I'm older I will prefer the robot to help me go to take a dump and clean me, instead of a nurse...
Of course the elderly and frail and people too afraid to touch something lest they break it will still call an expert, and original build and installations will need those trained, but I could see vast swaths of less technically skilled people opting for a go at routine repairs which could really hollow out the demand.
And where do they get the money to pay for this when all of the knowledge work is gone?
None of these end up really being out of reach of AI if Anthropic can justify this valuation. They're just slower to roll out.
If predictions about robotics are accurate, things will get even more difficult in the next ten years as humanoid robots mature.
Depends on timeframe. The economy depends on white collar workers spending money to pay for salaries of blue collar workers. The largestt tax-base is the middle class (white collar workers and blue collar workers).
Having 30% of white collar workers out of a job in a week is going to have the impact of riots in the streets, looting and a destabilisation (if not outright coupe attempts) of Governments. Might even be a partial collapse of some civilisations.
Having 30% of white collar workers lose their jobs over the next 10 years is manageable. We'll all be miserable, but the structure of civilisations and governments will remain intact.
LLMs are hugely suited to code because it's token heavy and the compiler is the RLHF verifier.
The LLMs are still very bad at concepts.
What we see in code does not translate to other, arbitrary domains.
Legal - yes, due to text heavy content with tons of great examples as well.
Everything else ... not really. At least not LLMs as we understand them today.
I'm not the only one that had that idea, they're advertising these things as features now.
I don't know what's next, but keep in mind that today's LLM's are the worst they'll ever be.
That's like saying in 2011: "today's Google search is the worst it will ever be."
Enshitification is coming my friend. We're just now starting to see the kinds of refusals that LLMs will ultimately end up with to protect IP owners and the status quo. We'll look back at this time and marvel that LLMs used to be able to reverse engineer software, or able to create derivative IP works.
I wonder if we are seeing them maxing out llm model capabilities now...
6.1 made a lot of assumptions and would "just do it." For many professionals that was a bad thing. For mnay users it was a good thing.
6.2 on the other hand does what it's told, and uses less flowery language.
I think they're focusing more on the enterprise.
But I wasn't talking about subjective experience I was talking about benchmarks like artificial analysis for coding agents, where it gets slightly lower score than 6.1 (frontier code 2.0 it gets a 2 point drop).
It was 100% different though, and it was a bit jarring. It was kind of like having one of your coworkers replaced with a similar, but different, pod-person. I'm getting used to that feeling though.
The one thing I think we can all agree is certain is that it will be different in a few months.
I kind of wish they had LTS versions of some models, so you could build processes and tooling around them with certainty that they'd be exactly the same in 5 years.
They are going to be 'better than what they are today' but I don't see obvious unlocks.
We need more abstractions on top of them.
Two examples of the lengths people went to for performance - 1) the networking hardware, terminals and everything were special airline flavors that sent data in 6 bits rather than 8, just to squeeze more data onto the wire. Is you look over someone's shoulder at an airline booking screen even now you'll see an all caps look - that's why. All caps means less bits.
The second was a little before my time but the geniuses who maintained the assembler code were very close to the hardware. Some used programming tricks to account for the rotational speed of the DASD, so the software would be ready to pull bits off the hard drive just as those bits rotated around and arrived at the read heads. Insane optimisations.
I'm out of the area now so I didn't know what the state of the art is, presumably there's not any IBM assembler still lurking but it certainly wouldn't surprise me.
The changes taking place now are not unexpected, and not unwelcome, but long overdue.
For anyone who nabbed the outsized returns while they existed, be thankful you got them at all, and hopefully you saved some of it. Due to geographic barriers to movement, 96% of humanity never had the opportunity to work in tech and profit off the supply/demand gap. LLMs arbitraged that gap, and now we can diffuse these capabilities throughout the entire world at extremely low cost.
AI is a giant compression and de-duplication algorithm on white collar labor, and it was needed. We've had an over-production of white collar elites problem for a while now resulting in policy errors in most developed economies who completely ignored building in the real world.
Don't worry, humanity still has more than a few problems to solve. There's infinite jobs to be done. The nature of humanity is that our expectations always grow to exceed our current capabilities. And with AI, you don't need to sit in a classroom for 6 years to get up to speed on the next job to be done.
If the US government allows it, of course. It just banned my country from buying data center nvidia chips.
>Don't worry, humanity still has more than a few problems to solve. There's infinite jobs to be done. The nature of humanity is that our expectations always grow to exceed our current capabilities. And with AI, you don't need to sit in a classroom for 6 years to get up to speed on the next job to be done.
You sound like someone who's overly cocksure that you've figured it all out. By It I mean, how to organize society. What Policy Errors would not have been made, in your scenario?
- The entire west relocating all key assets like factories, mines and production to the developing world/China
- Neglecting to build homes in basically all western countries for the past 18 years
- Virtue signaling going green by pushing energy production offshore to less regulated countries and then importing it back at even higher net carbon costs (more a Europe problem)
- Getting overly hysterical during Covid due to work from home being viable for the white collar class, requiring massive stimulus that mostly just caused inflation and inflated asset values
- Decades of under investment in hard infrastructure and instead investment in legal red tape and white collar bureaucracy
- An entire generation over-educated in digital building vs. physical building, such that much of the know how isn't even here anymore
- Post-financial crisis, inflating global asset values via artificially low/negative/0% interest rates to protect laptop class home values and 401ks over the real economy
- Over fetishization of credentialism/higher education -> government guarantees of college loans to any borrower regardless of ability to repay -> runaway inflation in the cost of US higher education
Want more?
A million Americans died.
Other than that, yeah, spot-on rant.
As you get older, I recommend traveling more internationally, you begin to get a more accurate picture of your relative stature.
While you and the rest of HN are busy exciting yourselves with the online bolshevik revival, it would be wise to first examine where you sit objectively relative to the rest of humanity (based on the analytics, if you're on this site you're in the top 2% to 0.001%).
If we're going to normalize seizing the property of individuals to pay for your fully automated luxury socialist dreams, unfortunately we won't be able keep the line drawn at just billionaires, or at just millionaires. The math doesn't math without taking your stuff too.
Under what historical precedent did we draw the line of “elites” at only the 3 richest dudes?
Sorry, we’re going to have to take your stuff too. There’s not enough Elon Musks to pay for what you want.
I'm already taxed. I just want them to be taxed as much as I am, not way less :)
I don't hate taxes, society or mankind (unlike some people on this site).
But I get it, you dislike the fact taking risk to build companies means you make capital gains vs. income (what you mostly get taking zero financial risk and working an adult daycare corporate job). And you don't want to try to create/market/sell something new that society finds valuable, you just want other people to take those risks and pay for you to live comfortably.
The problem: the 400 richest Americans pay about $40B in tax per year collectively (federal only, not including state). So how much should they pay instead? Double? Triple? 10X?
Even if they paid 10X as much it wouldn't solve the yearly deficit on the current government programs we have (we run a $2T yearly deficit).
Sorry, we're going to have to take some of your stuff too.
Just say you're a misanthropist, it's OK.
But of course, what does an old crusty fart like me know and what could I have possibly learned over 50+ years of coding that could be at all relevant today? IKR?
You hate this? That's on you. But doing the same thing over and over and expecting a different result is insanity. However, if you saved up before you were outed as an imposter, I can see that working out in the long run. IDIC and all that.
But the concern is overall jobs disappearing not “people Now have to be competent”
I live in a society and if there is suddenly only 2 jobs for every 10 it’s going to be a problem.
I also have empathy so I feel for people who will not be able to feed or house themselves because ai decreased then number of jobs.
you’ve still not answered what happens when or a solution to there being 1/5 the jobs available. Those people don’t vanish
Only time will tell, but I reject your pessimism on this. And I say that as a major cynic and pessimist on human nature. Shun! Shun! Shun the unbeliever in p(doom)!
This is just a tautological advice. It is equivalent to saying "be successful, then you will be successful".
Also, have you seen the batch of CS majors coming from non-top-tier universities? I don't see how they will be able to compete with LLMs.
So whenever someone says "We are laying off SWE's because AI", I have no idea what they're talking about. Just the idea of taking on the mental load of getting rid of engineers to direct more agents shipping complex features makes my hands sweaty. I am so glad I am still able to hand off the technical direction, architectural care, follow-up, unblocking decisions etc. to a real accountable human.
So yea, the sunset on this career seems far too pre-emptive.
So a company that can't/won't grow, lays people off and blames AI? Checks out I guess.
For them, keeping their level of ambition and dropping staff in favor of AI makes perfect sense.
A huge supermajority of users of those products couldn't care less if there are never any features added. They want a product that just works, that's understandable.
To use the Netflix example: why does a company that ships DVDs need to add streaming to their website?
Your comment seems to say that the higher cost of devs is worthwhile because it will allow a company to keep a lead, but how many products out there are just things like kanban boards, todo lists, and crud applications? Is any product ever completed and how much value really exists above the line at which most people are satisfied.
LOL, so true. I feel like as people at my (medium size, ~5000 employee) company start to really understand how much more software we can build, they're going to ask for things they've only dreamed about in the past. Just glorified CRUD, but that's what drives businesses these days.
Personally having been remote for ~8 years it would be difficult to go back to in person or hybrid, this said I am not sure how I could prove I am trustworthy besides "trust me bro" unless I am using somebody in my network as a reference...
If you hired a security guard to watch your house, would you be okay with that person watching a neighbor's house for a few hours each night because they had free time from watching your house?
People use things like responsiveness, turnaround times on requests, comparing timesheets to actual work delivered, and shared resources like updates to a common document to form an opinion about your availability.
I'm sure sales teams have the same issue. How do I know a sales rep on the road is actually making sales calls and not simply at a bar, day drinking? They have solved it by tying incentives to actual results and use CRMs to capture updates from sales reps to figure out if those reps are doing actual work or not.
Maybe remote software work needs to go the same way - tie pay to actual meetings attended and contributed to, tickets closed, issues raised which proved prescient in hindsight, and so on.
LLMs can help this sort of usefulness tracking. E.g., Give an LLM a meeting transcript and ask it to work out how much saimiam contributed to the meeting.
What's your product? You kind of need to provide that context - if your team is building some CRUD or calculator app that's a little different to a global engineering team working on products at massive scale.
> don't see a bright future for this profession
Then I'd apply the same logic to every STEM field. I'd rather have a CS degree and understand the tools that are supposed to be building the future.
I don't see a future where everything is AI yet people stop being educated in how AI and software works?
I did Mechanical Engineering years ago and we've had programs to do FEA and CFD analysis for a while now - yet we still have to learn how to do those by hand.
Put it this way - I don't think people who understand AI and software are going to be worse off in the future than those who don't.
I don't think it's relevant here. The point is that there were several work streams that kept several engineers busy full time that now are done by AI almost with little supervision. We do the same amount of work with less people and the software we ship is better on all relevant metrics. If the demand for software stays the same, we'll need less people for the same output.
> I'd rather have a CS degree and understand the tools that are supposed to be building the future.
Sure, we'll always need some experts. But it'll be a riskier career compared to what it was.
I think what you call supervision, I call care. Yes a company could always not care and ship stuff but you’re just kind of trundling towards failure.
I believe in modern parlance some people call it “slop” but that’s a bit of a flattening of what happens. Again, maybe you have a simpler product and doesn’t need a level of care across all dimensions.
It’s just not true for us, AI has made us more ambitious but also has rapidly upsized how much each member has to care.
It so is.
This could be another variation of "I don't need software engineers anymore for my business!" (it's a vibe-coded e-commerce site).
Went from a groups of team of 40 -> 20 and experienced the exact same thing. This was long before AI and agentic workflows though.
It was more a symptom of how much busy work / non-work was required to get anything done.
And if those “You are accountable for every line of code” directive holds here, they’re accountable for way more than they can comprehend. A huge win for the leafs in the org chart.
Leave each person you interact pleased that they interacted with you, better off in some way.
Engineers are now more productive than ever. Increasing productivity drives salaries up. Secretaries are paid more today than they were when they didn't have computers to use. Why wouldn't this be the same?
It was trivial for 1 Rails dev in 2010 to do 10-20x more than a Java dev back then.
Today’s world is an interesting dynamic but I’m pretty excited about it.
I tend to be more on the "Jevons" side of things, where I do think that demand will more or less expand. There are lots of projects I've been putting off for years because there would be an aspect about it that I hate doing and don't have the money to hire people to do for me (e.g. frontend web development). Those are projects that otherwise wouldn't exist that do now exist and potentially might make money or something (though with my business acumen that's debatable).
Java itself was a much slower standard workflow. Dynamic languages in general, like Ruby, Python, Perl or PHP were much faster to work with than the burdensome recompile workflows. Think instant feedback vs waiting for your CI to finish after every single save. The speed of iteration was critical.
Beyond that, when the speed of development is slower, more people get hired to do the work. When more people get hired to do the work, there's more communication relay as the team size grows. Teams coordinating between each other. Decisions going to committees. Middle management layers.
You'd routinely see companies with 3-5 Rails devs outperforming shops with 50 Java devs. Communication and iteration speed was huge. The other piece of it was the convention over configuration aspect because it removed so many things you'd have to discuss and make decisions about as a group which further accelerated communications.
10-20x multiplier isn't an exaggeration at all. If anything I could be underselling it.
On one extreme, a solo dev could prompt a frontier SOTA agent with not much more than "Build Uber", give it the necessary hardware/software/permissions to build itself a useful feedback loop and act autonomously, put it in goal mode, and let it cook, and as long as the tokens kept flowing they'd eventually end up with something reasonable in actual orders of magnitude less time than it would have taken that dev to build the same thing — especially if you're counting calendar days rather than hours worked, and extra especially if they wouldn't have had the luxury of investing full-time hours into that particular thing. At the opposite extreme, BigCo full-time SWE #5000 tasked with an extremely specific ticket for a critical revenue-generating brownfield system might experience even "20%" as liberal, and correctly observe that writing code was never the bottleneck for their job. And then there's the massive spectrum of circumstances in between those two ends.
None of that means that the gains aren't real, or that anyone in particular is wildly exaggerating in either direction. It just means the gains aren't evenly distributed.
If you're allowed to use the newer libraries and tools, it has actually been a perfectly fine language to write software in, even relatively quickly, since ~Java 8 or 11.
I have had elaborate fantasies of what I would do to the designers of JavaEE if I ever found them, and I had assumed that because writing JavaEE is so unbelievably horrible that the entirety of the platform was like that. Years later I had a different job that was much more amenable to me using "modern" Java, so I used Vert.x and Disruptor and properly learned how to use NIO and and I actually had fun.
I think Java has been the "regression to the mean" language primarily because it's taught to frequently in schools and it allows you to write in a very verbose and irritating style, meaning that it was a great fit for mediocre-to-incompetent engineers who want to look like they're doing a lot.
sigh
Not some greenfield dinky todo list startup project with 0 users
I don't believe this.
in aggregate there is not as much need as we can create now
If productivity increases lead to wage increases, being a weaver would be one of the best paid jobs today.
If it wasn't absolutely essential that a person was there, it would have been automated away long before AI.
My point is that MS Office has really automated everything about the job that can be automated. I don't think LLMs will really dent secretarial/PA work much further. Those people have their jobs not because the work hasn't been automated, but because their bosses are mediocre and relatively disorganised, like most people.
Silly Jarvis fantasies aside, an LLM cannot make your boss less shit at returning calls or managing their life. The people who need support humans will always need support humans, until they themselves are replaced.
Post computers there are now 50 who see 20% more income
LLM might get rid of a couple more but it's not going to make a major difference
There are now 10,000 SWEs
LLMs will drop that to 50 who see 20% more income
I'm sure you are one of the 0.5%
No it doesn't. Salaries have been decreasing in real terms over the last decade despite productivity improving. There was a period of time in which productivity increased alongside salaries but that does not prove causation.
Do you have a source for that?
https://www.marketplace.org/story/2026/09/04/wage-growth-can...
Obviously, the above is talking about labor generally, not just SWEs. But speaking as a professional computer scientist at a place with decent salaries and excellent benefits, my raises over the last 5 years have barely outpaced inflation. It’s pretty annoying to realize that I probably would have earned a lot more money had I NOT gone back to school for a PhD. Not that I would make a different decision given the choice again, but money is much more abstract in your 20s than it is in your 40s.
Likewise with garbage collection, OOP, and SQL. Each has greatly enhanced programmer productivity, and the result is an entire ecosystem of software that would have been too big and complex for programmers to develop using the previous generations of development tools. It has gotten to the point where we can sit here looking down on all those "CRUD web app crap" projects that programmers can throw together -- try to imagine building one using the languages and tools that were available in 1970.
In 20~ years we will probably be talking about all the generic "Agentic ABC/ZYX apps" that an entire generation of programmers builds their careers on and what it would have taken to build such things using the tools that were available in the CRUD web app crap era before coding agents. There will be more programmers, because people who are not programmers today will become programmers with these AI systems (much like Lotus 123 turned accountants and actuaries into programmers -- yes I know about the London whale, I am not saying there will not be problems that come up).
Then inflation eats up the salary, but doesn't lower the productivity requirement.
Also, there are fewer secretaries.
From https://www.bls.gov/ooh/office-and-administrative-support/se...:
"Overall employment of secretaries and administrative assistants is projected to decline 2 percent from 2025 to 2035.
Despite declining employment, about 314,400 openings for secretaries and administrative assistants are projected each year, on average, over the decade. All of those openings are expected to result from the need to replace workers who transfer to other occupations or exit the labor force, such as to retire."
Inflation is about the real price for a dollar, ie how many goods a dollar can buy. It's not about the relative price between, say, your labour and the goods and services you want to afford. Inflation is a red herring in this discussion.
The last 40+ years of data on wage growth vs productivity growth says otherwise.
Much better than the bad old days of the 1940s to 1960s: if you had told someone back then that in 2026 obesity will be a bigger problem for the global poor than starvation, they would have called you a crazy dreamer.
The gravy train for shoemakers was over. What remained was a small number of shoe designers and (initially) a large number of unskilled factory workers. Same with a large number of other previously skilled work.
But much will depend on how much professionally made software the world really needs. Demand for software could be a lot more flexible than the demand for shoes.
the market for SWEs will continue to be K shaped where the top of the K are SWEs that can solve ambiguous business problems and take accountability
The gatekeeping of making software is insane. Most people are building bullshit products for scum of the Earth corporations but they act like they're saving lives and changing the world.
We should all want more people to be able to make comfortable livings. If you don't want that, then you're pretty much the enemy of the people.
And more software does not necessarily mean more apps.
It does not.
Productivity increases and salary increases have been uncoupled for half a century
We’re talking about corporate compensation to labor vs shareholders and admin.
Why is there a steep decoupling on this graph?
Your argument is: automation making work easier is an appropriate reason to stop paying people comfortable wages, all at once?
I’m not convinced.
https://fred.stlouisfed.org/blog/2018/08/corporate-profits-v...
Because productivity measures all productivity, while salaries only track labor input? You do understand that in and around the 1970s we started adding non-human labor into the mix, right?
> Your argument is
Argument is for small minds. Facts alone should be sufficient for us to navigate this world. If I have misconveyed a fact then please do offer correction, but there is no need to imagine things completely out of thin air.
"Increasing productivity drives salaries up"
To which I said: No, that's not the case; productivity and salary have been uncoupled for a long time. That's a different claim from "salaries did not increase", which is what you are countering.
The wage-productivity gap is well known and I won't attempt to school anyone on it. Just look it up. Its really disingenuous to claim that the gap is going "to the robots". Robots don't give a shit. The gap goes to the _robot owners_.
It is the case, though. Salaries have been driven up with increased productivity.
> productivity and salary have been uncoupled for a long time.
This is also the case. Once we added non-human laborers into mix then obviously productivity would start to rise beyond salaries, which only track human labor. However, that doesn't mean salaries haven't also gained within increased productivity.
For a more apples-to-apples comparison you should be looking at the human labor productivity vs salaries chart, but I know that isn't as fun for the emotions.
Are you posting from 1990?
If they’re needed still, they are really needed!
My bank account disagrees with that statement. We are just expected to do more for the same pay.
I can name 5 other pieces of software I have open right now, more likely than not there are 100x supercharged engineers in this thread who work on them, and they're also the exact same piece of shit they were 2 years ago.
As a software user, when can I expect to see results of this unprecedented productivity boost? Are you people completely detached from reality, do you not see the output of the industry hasn't moved in the slightest?
You mistake “I don’t care about <feature>“ with “<feature> hasn’t been built”.
What about the other software you use? Just judging based on the software you use day to day, would you guess that we're living in an "unprecedented productivity boom"?
You can look at what happened to hardware engineers starting in the 1990s (if not earlier). Improved software allowed 1 HW engineer to do the work that was previously done by 3-4. Did this drive HW engineer salaries up? No, no it did not. It did the opposite.
As for secretary salaries, what's your basis of comparison? Women earn a lot less than men doing the same job. This used to be a lot more. So, if secretary pay went up at all (and I'm not sure it has in real terms) then how much of that is just eliminating the gender pay gap?
This is a commonly believed myth/meme that for some reason we can't give up.
No, increasing productivity doesn't drive salaries up. Unless that induced more demand for SWEs, which is not a given at all.
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
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
80% of people only use 20% of features, but if you build the 20% solution you only attract 5% of the userbase because they all use different features from the 100%.
I am starting to wonder if or when we’ll see that shift. If companies lay off employees because AI can fill the gap, the I think a lot of people expect those savings to be passed on. Right now, that doesn’t seem to be happening.
For my business the threshold is definitely getting lower for justifying building things ourselves.
Most of the "legit" jobs coming through my inbox are for grading LLM software tasks. A lot for long horizon tasks.
It'll happen when it happens, but till then I think I'll not be a party to that lol.
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.
I actually did. It doesn’t really change much IME. I just did it to come out in the open about AI use and start the slow adaptive process. It’s been a year now and just this week some colleagues are starting to act surprised by what is possible. I’m in software dev for crying out loud. This world is teeming with stingy sysadmins and neckbeards proclaiming it are all toys and soon everything will be back to normal.
If the culture doesn’t pick it up automatically there is some mixture of cultural factors holding them back and just knowing about tools ain’t it.
Hate to say it but most humans that couldn't code before because it was too technical also can't understand enough about the underlying systems to competently integrate AI.
I think we were a bit smug as a group. Sure we were disrupting EVERYONE ELSE and saying how disruption is just the natural way things work, everyone should adapt, etc. Now that we are the ones having to cope with the same thing, suddenly all that goes out the window.
I know I’m speaking in generalities here. I’m in the same boat as everyone else. I do argue that for those of us that have been into this since we’re kids, we grew up being told we were the exception. OUR jobs would never be obsolete, we are the future; we looked at people who refused to adapt with judgement. Now it’s our turn to adapt.
Indeed. I always call that out here on HN.
It was fine to disrupt everyone else. It was fine to replace all those laborers. If they complained, we just told them it was the implacable march of technology, told them to learn some new skill.
But now artists are getting automated and software developers are getting replaced. Watching people here treat it as a crime against humanity is just too much.
I'm a doctor. Putting me out of a job is and has always been one of the wettest dreams of hackers. It was palpable in every thread about medicine on HN.
Unless we can efficiently transmute atoms into other atoms I don't think this is happening anytime soon.
You can continue to code for the joy of doing it. If you enjoy the end result more than the coding process, you can work on crafting the best end result that you can. So it’s kind of a win-win for a true hobby, as far as I can tell.
I once reverse engineered my laptop's keyboard LEDs and made Linux free software to control them. Other people inexplicably found my project and built on top of it. I was really proud of that.
Then I subscribed to frontier LLMs and they made short work of that same laptop's entire firwmare blob in about a day. Solved some long standing mysteries. And I felt literally nothing.
This is one reason, but not the only reason.
I've been hobby programming alone for over a decade. When I subscribed to frontier AIs, it was like a shot in the arm. I finally had a coding buddy, someone to talk to about my projects, who would review and criticize my code. I learned so much I had to pause and let it sink in so I could understand what I was doing.
But the hobbyist niche I wanted to be part of turned out to be thoroughly hostile to LLMs and their users. I went from a guy who was interviewed in Lobsters for his programming language work to a guy whose work turned into slop essentially overnight, and the rift only grew wider over time.
So the sense of accomplishment is gone and now people whose respect I wanted call my work slop because LLMs touched it. This left me in this weird emotional state where I feel guilty for using AIs at all but know that it's impossible to go back to how things were before. It's been months since I've touched my projects. I just can't find the will to do it.
There's also the fact that AIs are changing society so thoroughly that governments are becoming extremely intolerant of personal computing and the subversive freedom it affords all of us. There is constant talk of AI regulation, and dystopian technology like remote hardware attestation is already becoming mandatory. We're also being literally priced out of computers. Everything we worked for will have been in vain.
I understand what you mean though in general; I wasn’t thinking of reverse engineering and things like capture the flags for example; when I think of those things, yeah it’s kinda “well I might as well not learn that now, I can just get the AI to do it if I need it”.
I’m guessing a lot of this is because data centers compete with gamers on RAM (and GPUs indirectly since Nvidia cares more about those product lines more than gaming now).
Once RAM prices come down to earth and China starts making cheap GPUs gamers will probably be the biggest proponents of AI since they’ll be able to use local AI to make games too.
When I finally subscribed to frontier AIs, it was like a shot in the arm.
Right. The sense of achievement is gone because there's no skill in paying someone or something else to code for you. It's the same reason Barry Bonds or Lance Armstrong generated so much controversy for their steroid use. Same reason Elon Musk got mocked mercilessly after it was revealed he wasn't the gamer he claimed to be. Paying someone to game for you isn't a skill. Paying a clanker isn't a skill and it's entirely antithetical to open source. But the hobbyist niche I wanted to be part of turned out to be thoroughly hostile to LLMs and their users. I went from a guy who was interviewed in Lobsters for his programming language work to a guy whose work turned into slop essentially overnight, and the rift only grew wider over time.
… because you chose to be the guy putting out slop. What is the point of free software if we can't run it? If running it gets us ostracized from digital society?
In what way are LLMs free in any sense of the word? Come on.You don't have to feel guilty about using LLMs, but why would anyone owe you an interview for that? Another "here's how I used Claude" interview is boring and out of place, even on someplace like Lobsters that's acquiesced to the LLM crowd.
We don't disagree on this, but that wasn't my approach in the projects I actually cared about.
I paid AIs to code with me: review my code, help me plan complex new features, challenge my ideas and the way I planned to execute them, teach me new skills. AIs taught me a lot of algorithms and data structures, taught me a lot of stuff about garbage collection and memory allocation, taught me about profiling and optimization... It was like an addictive drug for my mind.
> because you chose to be the guy putting out slop
Have you taken a look at my projects?
I have a few "vibecoded" ones, I never hid that. But I take serious offense to someone pre-judging my lisp interpreter as slop simply because I allowed AIs to work on it.
I spent almost unhealthy amounts of time and effort reviewing, editing and iterating on AI code reviews and output. Even the git history had to be right.
Would you consider Mitchell Hashimoto's ghostty to be slop?
> In what way are LLMs free in any sense of the word? Come on.
Free as in freedom.
> but why would anyone owe you an interview for that?
Nobody owed me an interview. I was invited to do one.
https://old.reddit.com/r/lisp/comments/1s8ri8f/how_often_is_...
> Another "here's how I used Claude" interview is boring and out of place
Don't insult veqq like that. His interviews are always interesting. My own interview mentioned AIs only in passing.
What, you're not doing trunk based development?
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
But I also see people complaining about frontier models writing too many helper functions, changing more code than necessary, and etc.
These are things that can be addressed through context engineering; AGENTS.md, skills, etc.
Also a lot of use cases require smaller, lower latency models. And these faster, smaller models to this day exhibit similar failure modes to 2-3 years ago and require very purposeful context engineering to get satisfactory results.
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.
It's going to be (already is) very disruptive. Which means a lot of opportunities and a lot of failures to be had.
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.
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 i’d you’re serving even the most basic app at scale with consequences, it’s so freaking hard,
a concrete real world example: literally msft outlook went down a week ago. it was out for god knows how many actual hours. this is technology that is “solved” and dumb simple in terms of complexity - it was out for what over 48 hours. and the status messages shared publicly were not confident. paraphrasing, but a message I got from their site was, “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 50 engs running around with claude asking the equivalent of, “please fix, no mistakes”
I’m not even sure the outage is fully recovered.
point is, yes there isn’t a giant 100 football field wide most 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 see it’s not that simple
The implication is far reaching. Lots of non-tech businesses which relied on expert help can now pareto slice it and hire experts on need basis unlike before. Saving money and increasing profits can be a big motivator to own many of those tasks too. Lots of people who were cosplaying as experts on non-tech people will have less and less opportunities.
Previously, being a knowledge worker could get you far, now the knowledge worker has to level up, and if opportunities are limited how could it happen? Even then, more experts (practice, not theory) is not a given, considering the bell curve effect.
I've got a friend in this situation too. He's going to hit a limit of what he can do with agents. And whatever agents can't do, his business can't do. We are going to find the shape of that soon.
Normally hitting a limit is where you would hire someone, but building organizations with heavy agent use is hard. AI is very very good at shifting work onto other people and business units; that's what all the complaining about review (and not just code review) is about. None of that responsibility shifting happens in a solo setup.
Build-or-buy decision is still very relevant, and one can go far with affordable PCB assembly houses, 3D printing, and many others. For a solo person, today's environment is 100x better than, say 10 years ago. So, niche businesses have better chances of thriving, all else being the same.
> I can’t help but think this anxiety and fear is just marketing. chill out everyone
never said that. I was giving examples of really low barrier to entry that has been incentivizing non-tech people to get more hands on than before.
buy-or-build and other existing setups for startups don't go away and if anything, they amplify what a solo can do.
>> I can’t help but think this anxiety and fear is just marketing. chill out everyone
> Here are few anecdotes:
Examples
> You are the one who is out of touch with reality.
Someone called on people to chill out, you responded with a dismissal of that sentiment along with examples of people setting up successful businesses. Connect the dots for me.
how is this different than the contractors who were also cutting corners before?
If anything, any motivated non-tech person can now use AI mechanisms to eli5, adversarial review, acceptance test, layman style documentation, to force the results they want. It was simply not possible before. Heck, if the contractor bailed, their shitty work could be revived too.
In other words, the verdict is still out on whether we'll see a decrease in jobs in the long run or not. Personally, I'm not very optimistic but, as I tried to illustrate above, I might very well be (and certainly hope to be) wrong.
Yes, we don't know the full effects, and sure things are in a flux, but let's not forget the convenient truth that the software engineering itself has required less and less expertise over the years due to programming languages with better abstractions, faster hardware, toolkits, frameworks etc.
With tons of jobs and better pay, lots of folks moved over to the web side since the level of expertise required (compared to a firmware engineer or asic designer or a dsp guy) is quite low and while the pay is way better. During the dotcom boom, a friend of mine who was a furniture salesman, took a java course and ended up with a software job.
Now, if the opportunity presents itself and incentives are strong, and barrier to entry is low, wouldn't more people also like to start/manage their business? I would think yes.
I'm building a mobile app using flutter. It's got to work on iOS and android. I can promise you, if I did not have years of experience, and I did not follow a regimented, checkpointed interaction flow with my agent, this code base would have turned to shit within a day. I've had to draw on my experience to define the architecture, correct missteps, prevent just wild flailing, and just generally keep things on the rails.
Your example 2 is the closest match, where someone with experience is driving the result carefully.
That's because your app has constraints. Why would a PT business operations and website for a side hustle need to be any more complex than the owner needs it to be? Your app complexity is probably trivial compared to say Google Maps, so your tooling is designed to match your app needs, not that of Google Maps.
Just to pretend that you are the only guy who can grok, and non-technical business people are incapable of curiosity, hard work, creativity and have the ability to manage their business and IT is more of a reflection of your mindset.
original post that we were replying to was https://news.ycombinator.com/item?id=50563851, which was:
> 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.
that was the context for your 3 examples, which is what i was replying to.
> Just to pretend that you are the only guy who can grok,
i never said anything like that. there is absolutely no issue with non-technical people who work hard and tinker and create, technology is for everyone, save money, do it yourself!
the larger point was about complexity, which is what we are agreeing on anyway. my point was that no LLM was going to one-shot what i needed, just like they're not going to one-shot what your second friend did, let alone google maps.
> PS: you are using llm to build the app too ;)
i sure am :)
I was actually responding to, quote '> I can’t help but think this anxiety and fear is just marketing. chill out everyone'
nice try ;)
I wish you the very best with your app!
idk man, my little sister produced an app (an LMS) with all the content, quizzes, tests, all the bells and whistles using ChatGPT to talk to ClaudeCode. She's smart but has no tech experience. her app is published in both app stores and she's gaining paying customers every day. AIs walked her through supabase integration, auth, and even the subscription APIs for Apple and Google. Also, all the paperwork involved in submitting, passing review, and publishing mobile apps.
I've never see a line of her code but the apps work and her customers are happy or at least happy enough to keep paying.
Sounds like your friend has learned quite a bit!
My impression of AI since the first ChatGPT has been that the best use-case for it is learning and research, and even with all the improvements in model capability, I still believe this. The "winners" of AI are going to be people who like learning (which is entirely distinct from, and in some cases opposed to, skill development--a knowledgeable, low-skill person is the kind that will do a good job very slowly. I think AI does devalue skill, but I think the elevation of knowledge and devaluation of skill has been the effect and trajectory of all technological development.)
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.
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.
Sadly more than likely they will just apply more and more AI to try to fix it, while others use AI to attack it faster than they can defend.
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 some shitty old RPG he made.
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
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.
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.
This turn of phrase really amuses me (whether I'm in complete agreement or not).
?
Speaking from experience I see areas where the need for software is indeed saturated after a year of AI-accelerated development (where the devs are really competent and proactive), but in other areas I see the demand for it skyrocket, even with no limit to Claude Code.
I also wonder what part of the "gravy train end" is the general economic rough patch we're in due to geopolitical conflicts & crises in the world e.g. Iran/Ukraine
Unless demand for software somehow increases 10x, this leads to 90% of developers being out of work.
This $$$ gives ANT much greater leverage to advance already very advanced models they have, and for us immortals this means that the future of SWE field as well as many other fields just became even more uncertain.
Some more interesting content on why is that so: https://institute.deepmind.com/essays/what-comes-after-agi/
Software just needs to be good enough to make a profit before it gets replaced by a slightly better or cheaper alternative, and we're probably going to see a plethora of those alternatives.
However I'm just some rando, I don't really know.
I don't really know either, just my mental health is torn to shreds due to that impending doom on the horizon.
If we step outside of our IT world for a second though, I see people who have it much, much harder already. At least in my country, compared to last couple of years, jobs are much harder to come by and right now it's hard for a lot of my friends in: marketing, social media, accounting, even management and business majors who recently graduated have difficulty to find anything entry level...
What's gonna happen in we go through a job erosion that suddenly dissapears half office jobs? Are we ready for a surge of unemployment and the ripple effects it will have to the rest of economy?
If it makes you feel any better, there are a lot of us in this position. Far more than talk about it.
I mean, I talk about it all the time but the main response I get is people who are somewhat relieved to learn it isn't just them. (Along with a different bunch of people who need to point out I'm being a doomer to suggest that it is remotely possible that things could get pretty ugly for our profession very soon).
It seems like many people are afraid to talk about how shaky the ground is underneath us for fear that mentioning it will manifest the worst outcome. And a lot of other people seem to be in denial that we could even really be at such an inflection point, clinging to the "AI is normal technology" idea.
I fully accept that my view may be overly pessimistic and things won't be as bad as I think, but I really don't understand how the people who are 100% sure everything is going to be just fine are able to maintain that certainty unless to some degree they are self-soothing as much as anything else.
It's kind of a tragic loss for people that enjoy coding like myself, but feel like decades of playing simulation games have prepared me for this moment of being a professional robot babysitter. I am attempting to turn these lemons into lemonade.
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.
LLMs won’t always guide you to do this correctly so you need to understand how important it is from the start and always enforce it.
Here be lions, since these things tend to lie to you or themselves when skipping the enforcement part.
If the software was capable of creating high complexity software I, or anyone, should be able to replace and build anything I want with just some prompts and guidance.
Anyone who has worked with LLM heavily knows this is far from the truth.
> I should be able to […] build anything I want with just some prompts and guidance.
…Yes? You can. That’s why some people are excited. The fact that agents can do a thing does not mean that you don’t (currently) need skill and taste to guide it in the right direction. No one said it was a magic button. Just a new form of cognition. And god knows I don’t expect all the human cognition I encounter in my life to be the image of perfection…Same goes for AI slop comments. I can just prompt AI into more or less writing like me.
> 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.
The people building those specifications and the tight validation loops you describe are the technical software workers of tomorrow.
Best, friend.
But, as @sama said, these models you see today are the worst they'll ever be.
It's only a matter of time before someone figures out how to maintain focus and drive a product to a polished end state over many iterations.
For example I don't see any mention that you ran debt reduction loops, code simplifications loops, and in general asking the model to clean up the code after it's initial phase of "organic growth".
For sure, the guys who lost out when automobiles displaced horses were the ones who were certain they only knew how to make buggy whips.
Adapt and thrive.
When systems get complex, someone needs to know them and know where to burn the tokens. You need to know what events need to be produced because you have specific consumers. You need to know your business invariants and why.
If you’re working on something that isn’t complex, yeah I can see why you’d think you can be replaced. If it’s just a front end? Yeah I can see that. A basic CRUD service? Sure. A business critical domain service with events, data migrations, complex business logic? I don’t see it.
It's not that I don't think those skills are important, but they betray a fundamental misunderstanding of what SWE is, which is about managing systems, juggling complexity, and having some wisdom about how those things should fit together.
Hopefully we start to better formalize some more of that now that the grunt work can be taken out of the equation a bit. And teach it in schools, find ways to measure it in interviews. etc
currently working on an initial product for a startup and while I'm substantially further along that I would be without LLMs, I'm at the point where the LLMs are now randomly breaking things.
There's typically a combination of issues that are occurring when the codebase goes off the rails.
One is that cruft builds up. Large vibecoded codebases need regular "review cleaning". Where you review the whole thing top down for hygiene, contradictions, bad comments, style, redundancy, design. It's a standard thing for me now. A full review and cleanup pass once every couple months.
The second thing that tends to go wrong is that after a certain complexity threshold, the models cannot keep track of the relevant details for a task very well. They lose sense of project directionality. Every task gets disconnected from other tasks and they start pulling the system apart at the seams, exacerbating the cruft issue above and accelerating collapse.
I've found that separating my documentation into three distinct lobes helps: goaling docs, guardrail docs, and implementation docs. Goaling docs describe in prose the goals of the project which includes scope, certain design targets, and other things that you are aiming towards. Guardrails are for design and implementation choices you have explicitly ruled out, the "what not to do" part. Impl docs describe the state of the system as it is.
The top-level agent documents refer to these and make their purpose explicit.
You'd think a ticketing system might capture this, but it doesn't really provide the richness of expression a collection of documents in a directory does.
These approaches aren't perfect. The process still has a tendency to wander off the rails, but it happens less often now and I catch it more quickly. Every session misses little bits of the goaling alignment, but they also find and address small issues missed by previous sessions. Overall it does a better job of keeping the codebase hovering around some threshold of coherency.
I'm having a lot of fun to be honest. Yes it's bizarre and nothing like what development used to be, but it finally feels like there's some new things to learn now.
These days they know how to handle their own context in review. So I will use that to find improvements too in retrospectivea and a small usage script hook it runs each push that alerts if high token usage. Hint the subagents are getting excessive context, which is also good hint of drift. So then I can measure when it starts happening typically via that script that Claude checks and readjusts when one goes over budget.
However it will be similar to cybersecurity in that there will be no 'entry level' product engineer. It will probably have requirements having worked in customer service or finance or some other adjacent field to get a larger picture of what you are delivering. You will also not need 3000 of these individuals anymore (did we ever really??)
I can see a world where you go from "AI Shepard Customer Success rep" -> some middle role with increasing 'product' responsibilities -> Product Engineer.
The new roles will also probably be more generic - instead of backend and frontend you have 'Backend' (Infra + API) and 'Frontend' (Frontend + Design) and both of these roles will require genuine product thinking
What we the people need to do is gain control and hold all the power of AI in our hands - not the filthy rich's hands! Devise systems that flip the power into our hands and create economies and jobs around it (i have ideas and surely 1000s to more do to around this).
No, and it's the same with leads, they can be given a system they understand but need to reference it.
I'm very certain these are people brushing up against their lack of processes, workflows, or engineering practices.
The context are large enough. You do not need to understand the world to build a chair.
I see the very opposite in many different domains happening now, and some codebases are monsterous. They are figuring out ways that do indeed work well.
The engineers that are figuring out these problems when working with a new tool, will have jobs.
Those who continue to doubt, and distance themselves are the ones that will be behind.
I think it is mastake to lay this completely at the feet of ICs. What you are describing is a form of engineering, and a lot of management feels that "engineering is solved" (not just "coding") and have no patience for these things. ICs are being forced into extremely naive and unsophisticated AI usage by managers with incorrect mental models. That's why so many ICs are cranky.
Its out there, it can do things, and it has its limitations. What it can do gets lot of light, and what it can't do well becomes a ICs 'skill issue'. Say with AI your velocity can go up by factor or X, but expectation is Y where Y >> X. This leads to lot AI-usage which is nothing close to "engineering". The whole idea that engineer should be able to defend what they build, while showing productivity gains that are factor Y can't be done without cutting corners, and it looks like leadership is mostly ok with it as long as it not immediately causing problems.
This is again not problem with AI essentially, but the overly optimistic expectations from it.
My other firsthand observation is seeing the difference between what quality of software that I, as someone with many years of experience, can produce versus my coworker, a talented designer without SW experience who is very AI pilled and excited to be making things, is able to produce.
LLMs have massively improved the quality of our company's main app. However, someone less skilled at our company tried to vibe code an internal tool and it was pure crap.
After about a dozen failed iterations I reverted to the last known working commit (albeit with the new module only partially implemented), isolated the issue as best I could, then asked Gemini again and this time it correctly identified a latent timing bug that was the cause of all the problems.
In short, I had to manually reduce the complexity of the problem for this magic infinity-dimensional-processor to deduce what the problem was. Maybe it would have gotten there eventually, but without AI I would have just reverted the commit a lot sooner and likely figured it out on my own with some basic debug logging.
It's still a net gain, as it's successfully one-shotted coding errors and bugs that might have taken me hours to find before, but it can miss basic problems as well.
Then after i understand it i can make a targeted investigations for that issue and after that it will be obvious for the AI, and all of those we still didn't change even one line in the code.
After that, we fix that issue (which is the root of the cause), release and congratulation the bug was fixed this way works even in lowest powerful models.
Through a combo of me and it over about a month we got it working well enough to roll out though. The entire time I had to hand hold the model through the changes though, and it loved to try and throw it away for quick fixes that would break something else.
It is hard to say how things will develop the coming years, but this sums it up for me today. Almost constantly, LLMs (e.g. Opus 5.5/Sonnet 5.5) make choices that a junior programmer would think is ok, but I know that will create technical debt, subpar designs, etc. Note that I'm not saying that LLMs program like a junior programmer, in many ways they program like senior engineers who have happened to memoize all API docs as well. But they are often missing the larger context or don't understand the time dimension (what will be hard to maintain, what will introduce an API that we can not easily backtrack from, etc). So, I am not surprised that vibecoding breaks down as a project becomes larger.
At the same time, current LLMs make me a lot more productive (which was not true for me ~one year ago). I can do in 30-60 minutes what would take me a day 1-2 years ago. In many ways, programming also became more interesting, because I can focus on design, the really challenging parts, while the LLM can quickly implement it. LLMs really feel like a different, in many ways complementary intelligence for development.
FWIW, I'd suggest that every major feature or change still needs review at the planning stage, at least. If you keep just requesting features without considering about whether the model's solution is the best (or at least, a good) solution, something will eventually break. That's not really surprising.
I think that's the conclusion you were drawing, also?
(In your particular case I'd just roll back to the last unaffected commit and try again, with a mind to how any solution might affect both performance and the viewport. Trying to fix what a model's already broken is a fool's errand.)
That could be as simple as raising taxes on corporate profits and using them for a universal basic income, or something more clever, but I hope governments manage to build something before it leads to a dystopia and social unrest.
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.
The only thing that makes this IPO notable is the dollar amount, and it is neither the first nor the last IPO to be notable for that reason.
Exactly...? This is the only one I'm sure to remember.
That seems highly unlikely, given that there are countless open-weights models available.
If nobody knows what your code does anymore, if it turns out that the tradeoffs AI makes metastacize over time, if it turns out that attention to detail ACTUALLY matters to the functioning of your systems (which it always has), then we are barreling for an extremely rude awakening. The water is just starting to move in the kettle - it might turn to a boil soon.
I am extremely afraid that are on the verge of losing coherence on all technology.
I've worked for some large orgs in the past. One thing that surprised me, probably because I was so early in my career, was how there was only a few, sometimes only one, who knew how the system worked. When something went wrong and that person wasn't available we'd all gasp. Then, after swearing a lot, we'd gather round and roll up our sleeves. Debugger statements, coffee, then when it got late it was beer. Rinse and repeat. Line by line. I see no difference now. If an LLM writes something and I can't rely on the LLM to fix an issue it created guess what? I go line by line.
(Don't assume that switching between different coding agents will always be simple or straightforward. It is possible, and I think likely, that in the coming years code written by one agent will not be easy for another agent to work with. It is already becoming difficult for human programmers to deal with agent-generated code and people are already starting to develop best practices to try to mitigate that. We are still in the early days here and we have not yet encountered many of the problems that are going to arise.)
Maybe it’s helpful to draw a comparison to the textile profession.
Looms were great for the industry. It makes it possible to have a product that people know about and can want.
Automatic textile machines were great for the production of fabric but very bad for the professionals who were paid a salary to make it. More fabric could be made, but fewer people drew a salary from making it.
Similarly, compilers, type checkers and other standardization tools are great for the industry and allow more people to become SWEs. Automatic software generators, to the extent that they can do people’s job, will not be good SWEs.
All of that is true even if you dispute that Claude Code can do a SWE’s job today.
As a 15 year old veteren in the systems programming space I have to disagree. You do not have to understand the codebase. You need to know the expectations and the invariants. Testing is also not the same as before, knowing how the system is supposed to behave is more than sufficient for 90 to 95 percent of the jobs. What you absolutely just cannot do is to not understand the design of the code that the AI writes, and still have instructions to make sure all the best practices in software and db design you have learn all along the way which too is readily available nowadays. A proper agentic workflow can do wonders in this regard.
Yes the code written are bloated but not necessarily runtime inefficient, but that's what most of the software jobs are about.
How would you become dependent on Claude? I'm certain they are trying their hardest at finding ways to lock you in, but at this point, there is no dependency.
AI workflows/skills/etc are independent of the model and company. Any comparable model will do.
Netscape.
That was the big one. Launched everything. Not in reality, but in perception.
The gullibility of people is astounding, and they never learn.
Everybody is an architect now.
Don’t worry.
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.
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.
I think almost every new business will have at least one person whose job is to deal with the technology. There might be fewer of them, and they might be a weird amalgamation of sysadmin and web developer, but there will still be jobs for nerds like us who actually like doing this stuff.
Capitalism is inherently broken if people don't get paid wages, because then they don't have money to buy stuff. Fortunately, capitalism doesn't need to exist forever
vs
"I want to pre-sort during idle time so that I can effectively implement a binary search"
You can tell me either of these and get the same product. You can pick one of these and tell an LLM to do it three times and get three different products.
Sorry, this cope.
Now, this may be acceptable (tons of businesses are built on broken products), but what is absolutely cope is this moronic idea that the LLM is always smarter than the average engineer and will magically produce the most efficient and correct solution.
Yeah but the person you're replying to isn't gonna see that because they already made several assumptions about the problem I put in front of them
And if I still want professional help then there will be a excess of labour due to the above for most tasks.
Disagree.
What is worse is having to learn and do it yourself because the people you hired won’t do their job properly.
Waiting = not paying attention to the issue = nobody cares (unless it’s some emergency). So what if your taxes are done two weeks later??
We'll be fine. Move to a lower cost of living area, start a business. There's millions of companies in need of software expertise.
All this moral panic about software work is unseemly. Maybe the easy "learn JS/frameworks" path to wealth is closed. Whatever. Good, actually.
We'll be fine, we're the most prosperous worker class in the history of working.
Besides the job never was churning out code and if there was a bloat of such positions it was only ever a temporary distortion.
This reminds me of that viral clip with Ben Shapiro saying that if the sea levels rise, people will just sell their homes and move. The clip went viral because of the response: "Just one small problem. Sell their houses to who [sic], Ben? F*cking Aquaman?"
> All this moral panic about software work is unseemly.
You know, it's funny how the history keeps repeating. This will be far from the first time a technological breakthrough left a group of people obsolete and scrabbling to deal with it.
Every single time this happens and ends up being a net positive for the society, the suffering of those people is ignored at the time and then we eventually look back and end up expressing empathy for them. And every single time we express hope that maybe next time we can do better as a society.
And every single time it happens, we not only fail to do better, but we have people condemning the very idea that we should even try to do better.
> Maybe the easy "learn JS/frameworks" path to wealth is closed. Whatever. Good, actually.
Wait, I could have easily amassed wealth by "just" learning "JS/frameworks"? Wow, and here I had the wrong idea about the causes of wealth distribution inequality. It's clearly those parasitic JS devs' fault.
What's going to change is that we'll have to focus on the actual hard problems of software development: making sure the software does what it's supposed to, isolating nontrivial bugs, finding ways to make it perform better.
These are exactly the things LLM's outperform all of us on.
If you've tried to build anything nontrivial with LLM you know this just isn't true.
Why is much of our legacy software suddenly failing us if we are so much better at finding intricate bugs than the LLM's? Why are all of us easily capable of speeding up our software by orders of magnitude in small amounts of time utilizing them. Yes, they are better at verification as well.
I share a similar experience with bug finding; I think it also helps that LLMs can simply hold much more context at once than a human, as seeing a much larger portion of the codebase simultaneously makes it much easier to spot discrepancies.
As for legacy software suddenly failing us, what you're really talking about are active systems like Microsoft 365 (it's not legacy code). Those systems have always been complex. That they are "suddenly" failing could be an indication of a number of things, but I'd pin a large part of the responsibility on organizational debt (even beyond technical debt). Maintaining complex software systems is hard, software mostly isn't a static thing it has to constantly evolve. It could also be an indication of over-reliance on LLM competency, for all we know about those system's internals. We just don't know enough to make an assessment.
There have been some zero days discovered by LLMs. There have also been many socially engineered, regular old exploits that have been impressed on us as indications of AI breakouts.
As for speedups, most software is comically unoptimized and has been for some time. We made an explicit trade-off in software development as CPUs and machines got more capable: we started coding in simpler languages with higher levels of abstraction (Python, Ruby, JS, Java, etc) sometimes costing us 10x or more in resource utilization, in exchange for the iteration speed that bought us. Converting those to more efficient languages like Go, Rust, C, etc alone buys you so much. On top of that, there are a number of algorithmic optimizations most developers never implemented that map to well known access patterns in hardware. Lots of low hanging fruit.
Examples are: Note taking apps, voice recording apps, calendar apps, video games, etc.
They'll shove out a pattern quickly, but no matter how new and magical the latest model is, they will just put out some tweaked variant of existing designs. I find myself treating it like a junior-mid engineer. "Add rdtsc-based timers around major parts of the code to whittle down what's taking too long." "Use that to figure out where the transfer amount is way too small to justify the time taken without copying the payload." etc.
But concurrency bugs from large LLM-developed codebases are a major issue. They constantly find bugs they wrote. I eventually told it to start writing formal models of the concurrent uses and to (a) validate the models; (b) verify the code implements the models; to make it work.
So yeah, I stand by my words. For simple commands and tiny codebases, it /can/ do those things, but even small projects (50 KLOC) are a mess of making it fix its own mistakes, reconcile basic logic in requirements analysis, and everything has to be taken over with a fine-tooth comb to make it any good.
If you don't specify the model you are talking about, you have written a sentence with near-zero information content. If that's your habit, well... that's likely part of the problem.
I promise you, Fable and Neon are better than you are at pretty much whatever. Sonnet 4.X and MechaHitler, well, maybe not.
In a similar vein public clouds contain the components to built any software you can think of. But that doesn't mean that all the solutions possible spring into existence just because AWS exists.
The tools are amazing, but I think they are most amazing when you can have deterministic verification loops. Async bugs aren't always encountered, so it's a little more difficult for the LLM to prove its work and iterate. At least, that's my current hypothesis for why it tends to degrade so much for this type of problem.
If you throw an excessive amount of money at the problem yes.
Wages might decrease if the work becomes easier and more people are able to do it, but I'm not sure jobs will actually go away until true AGI.
How does this work? Care to elaborate? Doe the wants remain infinite but no one willing to pay?
Seems like copium to me if we're being honest.
Why would anyone pay you to solve the problem when they can just throw it at a cheap LLM?
And if the answer is that you have some sort of special taste or domain knowledge, once your solution is out in the world how are you going to stop someone from using an LLM to copy it and then undercut you in an immediate race to the bottom for everything?
I don’t know what moats we can have at this point. I’m trying to build a side hustle with vibe coding something because if it’s a backend only you can access at least you have a tiny moat. If you’re just prompting slightly more cleverly at your employers Claude account you do not have a moat
i also wonder if there's something in your employment agreement about the things you make on company time and who they belong to.
If that happens I guess the whole thing hinges on how powerful and user-friendly open source models become.
It’s not possible for them to grow as big as their boosters want them to. There would be so much resistance, and if that resistance fails, then we’d already be in the middle of techno-dystopia hell anyways, where money wouldn’t matter.
government will be their puppets, and what can I do then?
if your scenario starts happening, we break up anthropic and openai for antitrust reasons, or people do other things so that they don't become kings.
If the answer to that is "yes", then there's literally no point in anyone hiring anyone for any knowledge work. And that applies to other businesses. Why give a SaaS company recurring revenue if they're just a thin wrapper around Claude anyway?
The answer I think is that few companies are so thin. Most offer something else, some other kind of moat that has nothing to do with problem solving, or some kind of lock-in.
But there are definitely some (mostly small) companies that only exist to sell relatively simple specialist software to customers that don't have their own developers. Their moat against competitors was the relative scarcity of good developers, and the difficulty of motivating them even if you could hire them. In the post-LLM world, those small companies suddenly have competitors for the first time...
In my necks of the wood (mathematics and foreign language education) we seem to be plumping for "human understanding and communication" as the new USP. I don't have too much faith in that supporting a lot of jobs but we'll see.
(1) LLMs can solve any human problem; (2) that #1 would be a bad thing if it were actually true because some SWEs can't get the same job they had before
if the LLMs are that great, tell them to find the SWEs a new, better job. if they aren't, and LLM+SWE is > LLM, then #1 falls apart.
Certainly not every problem, but enough problems that we currently consider economically valuable to cause a very large negative disruption in labor.
> (2) that #1 would be a bad thing if it were actually true because some SWEs can't get the same job they had before
I wouldn't say some SWEs I'd say almost all SWEs.
> if the LLMs are that great, tell them to find the SWEs a new, better job. if they aren't, and LLM+SWE is > LLM, then #1 falls apart.
Again, I don't think LLMs will solve every problem. Just enough problems that they put about 80% of all knowledge workers out of work in a relatively short timeframe, which is going to be economically disastrous in a way that expands far beyond just knowledge workers.
My grandfather worked at NASA, and my impression is that a significant portion of what he did was actual calculation. Nasa still employs people, they just don't do that particular work anymore.
On the other hand, just two years ago they were practically useless for anything non-trivial. In that time, they went from "might be cool someday" to "can do most of the work, but still needs handholding." What are they going to look like two years from now? Five years? Ten?
So much depends on where we are on the S-curve. If we're getting into diminishing returns, then we may top out at a point that isn't too far beyond what we have today, where they're highly capable but need that human judgment and oversight. If we're at the bottom of the curve, it's hard to know what the future would look like. I have no idea which one is closer to being true, and I don't think anyone else does either.
I think we actually are there in some areas but the bureaucratic/social structures are actually blocking it. If you asked me 2 years ago I would have laughed.
The existence of companies like airbnb or uber or spotify confuses matters because they pretend to be software companies with valuable software but their real USP is some kind of legal/regulatory/market dominance and their software is nothing special.
There's been the very occasional breakthrough, but it could have been done by just a handful of brilliant people at key moments. The rest was just filler and AI will do it better than we have been anyway.
They only know about things they’ve seen before, how could they ever come up with something new?
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
We had prevented this for 20 years in the 1950s and 60s with a 90% federal tax bracket that capped yearly incomes to $5 mil a year in 2026 dollars. Stock buybacks were illegal and we had a bunch more post-1929 regulations that were not gutted yet.
Restore the tax policy and financial regulations of the 1950s. CEOs would be stopped immediately. This is how we got out of the great depression.
Ever played Monopoly?
So yeah, that is actually the one area where they’re not equivalent to dividends, tax treatment. Though that’s changed in the last twenty years as well as some dividends are no longer taxed as individual income.
https://boomersbrokeamerica.com/stock-buybacks-illegal-1982-...
https://www.investmentwatchblog.com/stock-buybacks-have-only...
Buybacks will select for frequently traded shares that have little gains, as well (this is just another way to say the above).
Ofc the elephant in the room w.r.t. capital taxation is tax advantaged retirement accounts, which have much, much higher contribution caps than was ever intended (how many people can save 80k net per year? Not many). Something like 75% of all public equity (by value) is held in advantaged accounts and exempted from capital gains taxes completely.
stock owners gain a lot more from buybacks than dividends. Juice your gains. Die. Dont pay taxes.
Buybacks likely also increase liquidity/market efficiency which is a stock owners benefit [0] (companies buy when price is low to prop it up. increase liquidity. also sort of relevant to today i was learning how the ANT greenshoe works).
Even if you do eventually sell you've basically gotten an interest free loan from the govt in deferred taxes over your hold time. that's huge.
what matters more to me is that it probably drives inequality.
100% proven to definitely decrease tax take (found different sources from about ~400-850bb 10 years). That's universal pre-k + universal childcare. Or free community college + school meals for all. OR pfml + dental and hearing in medicare.
One study [1] compared the same person same stocks > taxable v. IRAs/401ks: "Effective accrual tax rates for stocks that experience substantial appreciation are substantially below the statutory tax rate on long-term gains." e.g. lower effective tax rates/ever shrinking revenue sources
the 1% tax in IRA barely makes a dent.
This study is a triple wammy of gross [2]:
- illustrative of executives who get comp in stock seem to be more likely to make selfish short-term stock price driven decisions - use last-minute buy backs to juice earnings (prob voids the put benefit) - at the expense of R&D and re-investing for innovation
" share repurchases that increase earnings per share (EPS) is sharply higher for firms that would have just missed the EPS forecast" "EPS-motivated repurchases are associated with reductions in employment and investment"
[0] https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2506671 [1] https://www.aeaweb.org/articles?id=10.1257/00028280577501446... [2] https://www.sciencedirect.com/science/article/abs/pii/S03044...
This isn't a buyback issue, but a step-up basis issue.
They were illegal up until 1982.
You may argue that regulations, such as banning of stock buy backs, could hinder such a trend, perhaps so, but over time the more capital and power accumulates, the more the laws and regulations will stack in favor of the capitalist class, ergo oligarchy.
Using the 1950's as a justification for policies you support is disingenuous because the real reason the 1950's were so good is because the USA had just won the largest war in history without any damage to the homeland and had the only industrial base that wasn't bombed out and exported a huge amount of manufactured goods to the entire world.
The policies you advocate would just privilege the existing holders of capital by making it impossible for anyone new to join their class. It would also lead to all manner of bizarre forms of perks, kickbacks, and other non-monetary forms of lifestyle benefits and power, sort of like you see in the ruling class in communist countries.
It was a bit of a disaster.[1]
Then he saw the Autobahn in Germany.
He also was Sir Arthur Tedder's superior at SHAEF when Tedder developed the strategy to destroy Germany's railroads.[2]
It is not surprising that Eisenhower was committed to the creation of a national highway system.
Then you have him the reins of the massive public works machine built by the new dealers, and the interstate highway system is practically the inevitable result.
[1] https://en.wikipedia.org/wiki/Transcontinental_Motor_Convoy
[2] https://uncpress.org/9780807858509/the-collapse-of-the-germa...
So why did the UK also see the emergence of a strong middle class which has since eroded?
CEOs are allowed to do all of these things, but they do not necessarily maximize business returns, and therefore their own incentives. Nothing has changed here from 2020, 2015, or 2010 -- a period over which SWE compensation has skyrocketed. No reason to believe this gets worse with AI.
The 50s and 60s marginal tax rate was (1) mostly paid by no one; rich people instead received business income not subject to personal income tax; and (2) other high rates were only possible due to a sense of national togetherness forged by the world war. There's no reason to believe this time period was exceptionally good for the poor, working class, or middle class.
It's easy to hate the rich and want to punish them for being rich, but it doesn't help the poor to do so.
0.25% is what today's billionaires consider "punishing." Absolutely wild. I pay tax at more than 100x that rate.
It’s not spending or even loosing the money, it’s helping other people that he hates.
The US federal government spent about $7 trillion last year. Only a tiny fraction of that is "broad social programs" that are funded out of general tax revenue.
Obviously taxing anyone at 100% of assets is wrong. I just take exception to bad math.
A more reasonable 1% of assets for the top 1% would net $400 billion annually (again only their public stock holdings). That's almost half the defence budget. And 1% is nothing; the stock market goes up 8% on average so they still come out ahead.
Correct, because the mechanisms of capital were different and the system encouraged utilizing it for material investment and keeping labor happy, which is where that business income went.
> other high rates on the middle+ class were only possible due to a sense of national togetherness forged by the world war
What alternate timeline did you come from where the 1960s was not a time of major cultural rift in the US? Do you think the upper middle class was not a huge source of hippies?
https://archive.org/details/CSPAN3_20180512_120000_Reel_Amer...
> There's no reason to believe this time period was exceptionally good for the poor, working class, or middle class.
What? Wealth and income inequality was at its lowest since the founding of the country. An effect which was established prior to the involvement of the US in the war, it began with FDR's new deal. And once they hit the floor in the early 1940s, the numbers were extremely steady and consistent until the financial system overhaul in 1975 at which point they shoot right back up again. There is no reason? Every single metric disagrees with that, except for racial inequalities. Enough with the neoliberal apologism, Gordon Gekko.
The 60s is the tail end of that period, yes. Tax rates were cut significantly in 1964.
>
The 60s is special because it was a great period of cultural divide, I pointed it out specifically because you were painting the period as a time of national unity, indicating you don't actually know what you're talking about. But the idea of a strong national unity is, in general, just rose tinted goggles and historical ignorance even beyond the 60s. It was the absurdity of explicitly using that decade as an example that deserved pointing out, because it demonstrates either ignorance or dishonesty in the argument to the highest degree.
> And yet, the poorest 10-20% didn't have refrigeration, ~1/3 didn't have indoor plumbing, 6% didn't have electricity
Also almost nobody had air conditioning.
Anyways, these are all drastically lower from what they were in the 1920s. Is that because the system prior to the New Deal couldn't distribute them? No, even though the system was measurable worse as far as equality is concerned. Even discounting the geographical confounding factor here, the build out existed and at a higher rate across the population, not just in the long tails. These numbers changed (though miraculously, still haven't hit 0, or even a vanishingly small number) in spite of a different system, which measurably was actually worse. Or were you actually going to elaborate on why this percentile was ONLY capable of receiving these amenities after the economic overhaul in spite of the clear trend of change pre-existing the overhaul? That's a rhetorical question.
> they had almost no healthcare to speak of
Access to healthcare has become worse, actually, not better. Virtually every single working family, not living in the middle of nowhere, had access to healthcare in the 1950s and 60s. That is no longer the case. Simultaneous to this, rural access to healthcare never really improved.
At the end of the day we have to consider your argument has now mutated into the idea that the absolute poorest are better off because the richest are richer. Relatively speaking, they seem be much worse off as a matter of fact. Your causality simply isn't justified, it doesn't even correlate, and when given the slightest scrutiny, all the arguments can't hold water without disingenuity and dishonesty. Especially when it's continuing the grave sin of focusing on the long tails.
If we can’t afford the same in America with 80 years of additional technological progress and war never touching us that is a policy choice.
just happened on a client call yesterday. our work had been postponed because a new system was being introduced. our routine calls kept being cancelled and we started to worry. the customer finally showed up after a few months and told us the new system was demoed and "was clearly vibe coded. everything went wrong. they were asking claude questions during the demo" so were back in contract again
> reliably deliver them better than 50% completion
everyone has ideas. being able to program helped separate ideas from execution and i thought llms would remove that barrier but there seems to be some ingrained half-ass mentality in the self-proclaimed "idea guy"s ive met which prevent them from finishing things
Next time, the client will skip you and have AI do it.
Then later, their client will skip them.
Until you get to the actual user.
im not sure if its just that LLMs will get better to the point where everyone WILL achieve their goals, or if its always going to be the case where everyone COULD achieve their goals but most simply dont. will tech solve this, or is a human problem?
“Is your vibe coded ATC system grounding flights nationwide?”…
there is shortage. You can just jump on problem you want to solve, because distribution channels are saturated/occupied.
Anecdata I’ve seen this too a few times. Major issues where a significant number of engineers had to stop important product work to un-jankify something a non technical person created. In every case those product people felt the heat so bad they basically stopped.
Seriously, you need to go outside dude.
Right now there are mass layoffs partially as a correction to the pandemic hiring spree, and also to redirect capital from salaries to AI initiatives.
It is fashionable right now for tech CEOs to pretend that enormous amounts of work being done by humans is now being done by AI, but none of these are companies where the velocity at which code was written was ever the main bottleneck in getting products out the door.
The software industry is overexposed because there are a lot of people earning hundreds of thousands of dollars a year to add fields to CRUD apps. These folks are in enormous danger, but when the dust settles the skilled professionals solving difficult problems will do just fine.
I guess I kinda resent your implication that the "skilled professionals", the worthy, you know, us, will be fine. I think the real danger is for the people who care. And for the rest of us who rely on the people who care.
Just look at the job offers and the responses they get on here. It's all trivial crap.
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?
But once people catch on to this dynamic, I doubt people are going to be helpful in these onboarding the AI guy jobs... It's a reaping, boil down the heuristics they spent a career building into a document tree, then push them out.
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.
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.
SWEs who oppose AI seem to forget that they are paid to solve problems, not write code.
Moreover, big picture, software is getting built anyway. It’s not like if you don’t use AI then that energy use is gone. You need devs no matter what.
Some countries are making laws about renewables requirements for datacenters. Generally they are structured as "gas is allowed as a backup but there are big fines if it is used more than X days a year", and then let the market decide what mix of solar + wind + batteries wins.
The US should do this too.
Capital has historically and enthusiastically done exactly that.
The reality is humanity itself pushes forward in a way that often steamrolls those who don't keep up. Nobody's driving the steamroller intentionally, yet it invariably inches forward nonetheless.
Yes, and you've even explained why:
> People start businesses [...] because they hope to make a better life for themselves.
Not for anyone else — for themselves. They do this by exploiting others.
People can be exploitative, but there's nothing inherent about it any position or another. Taking money for labor you intentionally half ass is no less exploitative than e.g. trying to coerce an employee into doing something they shouldn't be expected to do.
So the Walton's money printing button comes from taking 3 pennies from each dollar, but at a very high volume. If Walmart wanted to e.g. significantly raise the wages they pay, they'd have to substantially increase the prices on everything sold. The balance of higher wages for some but higher costs for all would almost certainly be a significant net-loss for the lower half of society.
And this issue is even more pervasive at smaller shops. Making ends meet is even harder for small business owners. The idea that somebody's just printing money because they own a business is unrealistic. Well it's kind of true for tech businesses, but I suspect we're going to see that change in the future - though that's another topic altogether.
Like, just because the Walmart owners own a company in a low-margin high-volume sector, they're suddenly entitled to the 3% profit, while the employees often need government assistance to keep themselves afloat...?
I'm not arguing that WalMart is socially motivated but that margins in non-tech businesses are not at all like most people think. They're slim with massive sounding outcomes (like $21 billion a year in profit) coming exclusively from scale. Redistribute that back to the employees to the point of self destruction and it's certainly a substantial amount, but far below the level many seem to think, on these topics.
The irony is that it's the companies that people think are 'generous' that are hoarding massive amounts of $$$. Apple makes something close to a million dollars in profit per employee, so they could afford to literally buy every single one of their employees a new Ferrari, every single year, and still be rolling in profit. But these sort of insane tech margins are not normal. More controversially, I think they're also not sustainable in the longrun - and the longrun just got a whole lot closer with LLMs.
So that would be what, 60-70%? IMO that's wildly unrealistic, I'd need to see actual evidence to believe they are so far off the norm.
> WalMart's 3% profit margin is about $21 billion. Coincidentally they also have 2.1 million employees. So the math works out perfectly - a one-time raise of about $10k per year per employee, at which point the business would be unprofitable and no longer sustainable.
How is a company that's breaking even no longer sustainable?
The reason that breakeven companies aren't sustainable is because there's variance in most things, certainly including sales. WalMart's net profit margin varies from around 1% to 3%, so they're currently at a 'high'. Cut that down by 3% and you literally don't have enough money to pay your employees next year when you swing low. Let alone little niceties like performance incentives, raises, etc.
No matter how cute you try to make it sound, when one person owns the land and the other person works it in exchange for pay it's the person working it who is exploited.
Some people like to hand wave the question of who owns land and why they own it away but control of that wealth is always rooted in historic violence.
You can take away any and all land. Imagine somebody thinks a public park is in nasty shape, so they hire a few guys to go help them clean it up. Is that still exploiting people? This all just makes no coherent sense whatsoever.
capitalism is founded on the divide between those who work for a living and those who own for a living.
governments pay people to clean parks. it's not something a private citizen would typically ever do.
Often maybe, but not always.
Avoiding displacing human labor that doesn't want to be displaced is always something I've thought about before any job I've taken.
No putting clankers before humans, no grifts, scams, pushing ads, gambling or incentivizing other forms of addictive behavior.
Fairly simple rules to live by, though it does mean there are entire major companies (and entire market categories of companies) I could never work for in good conscience.
I do find the fact that AI is disrupting us software developers first and foremost seems karmically fitting in general.
unless when combined with robots.
That is why I think AI is more of a service than a tool.
I am not sure what real problem my barber is solving. I am physically capable of using scissors and clippers and learning how to cut my own hair. But at the end of the day, I rather just pay someone trustworthy to do it instead.
The money I pay is worth it for me to not have to deal with any of the previously mentioned tasks.
That's a great point. It's easy to forget. I can also make food at home, but often prefer going out for convenience, skill, etc.
Most people don't do this for the love of the game.
Large corporations needed java code as a means to an end and an army of workers needed a paycheck. That dynamic is coming to an end.
Solving problems is not distinctive characteristic of a software engineer, doing it by writing code was.
That being said, software (written by hand) has replaced many craftsmen. It’s a bit hypocritical to bemoan AI taking away our need to write code line by line. It’s what we’ve been doing to others since the first computer started computing.
There used to be "typing pools", whole floors of mostly women who typed handwritten and dictated notes up into actual documents that could be filed and distributed.
I heard this week that there used to be seven draughtsmen per architect, and now there's one draughtsperson per seven architects.
So, yes, software has completely replaced entire careers. We can't really grumble when it's our turn.
I suspect programming will be similarly forgotten in the future when any program can be concocted trivially and efficiently by description alone.
Much like potters used to be a profession that was needed in every community, and now they're "ceramic artists"
People on hacker news like to think they are Picasso but the reality is 50% as good in 5% of the time has always been better from the business perspective.
But so are all the cyber enslavement stories.
We make aggressive decisions, based on overly optimistic bet on "AI will fix it" mindset. I think it should be more towards, given what we have now and may put in little bit of optimism around AI how can go forward without completely dismissing decades of engineering principles we developed. If AI really goes 10x better than what it is now, then we can just build stuff much faster then anyway, but it didn't we made something reliable today as well something we can keep building on 5/10 years from now.
What does "lets think about it a bit" even mean though? You want other people to stop using productive tools? Or you want to be able to opt out of using productive tools without an employer worrying about it? There always seems to be either a shifting of burden to others, or a denial that AI tools increase productivity.
People can think about AI and use AI with all gas and no brakes. Or you can opt out of using AI for as long as you like to think about things.
Don't push code no human has read into production.
> Don't push code no human has read into production.
So you don't want to do that in your production environments? Or do you want others to not do that in their production environments?
I don't understand the question. I didn't give two options.
> What if "let's think about it a bit" is about your coworkers going head first into a design that you know will fail, and then maybe let's think about how we can do a better design before we lock in a shit one. The AI does build _exactly_ what you ask, whether it's a smart choice or not. Surely you can just automate that choice to the AI as well, why not? "Think about all the ways to design this and pick the best". But possibly we are being led blind into a tar pit. So maybe, just maybe, we can spend a seconds of our lives to try to involve our human domain knowledge and hard won expertise at this job and its systems to guide the AI in a more productive route. Or is this scenario really just about slowing down everyone around you because you're secretely an indignant, neolithic, asshole.
Having different perspectives and advocating for what you think works best, how to use tools, how to approach problems, has always been a thing and always will be. People where I work have a lot of different ways of using AI and share ideas and techniques, for example. Telling someone to not do what they have found to work with things like "let's think about it a bit" doesn't work though, that's not collaborative, you don't just tell others to stop and think, you have to actually do some thinking yourself and come up with constructive ideas. Doomsaying or vaguely handwaving at how bad things might be doesn't work either. It's like telling farmers they shouldn't sow their crops because you're concerned the gods might be angry and smite the village so they should stop and think about it a bit.
The reality is that AI is a very productive tool and it is never going to be stopped now. Bad things could come of using AI, bad things could come of not using AI, a bad thing could happen when you walk down the street tomorrow. A lot of people are scared by it, but really just saying things like "let's think about it a bit" betrays the lack of thought that has gone in to understanding why other people use it and how people react to that kind of thing in general. Not really surprising OP has seen a bit of apathy or hostility to their message.
This is the EXACTLY the kind of BS you get. No, not asking you to stop using those tools. Its not 0 or 1 thing. Its not a choice between "all gas no brake" and "I wont use AI". But maybe, just maybe, think a little about what you are producing, instead of just being a ENTER PRESSING entity. The amount of spaghetti that is being generated is not just an issue from the perspective "oh the code looks horrible to read", but also fundamentally how we build complicated systems, and it becomes bandages over bandages that just sucks and potentially fragile.
The alternative is don't go all gas, work strategically thinking a bit longer term like we always had in past, and maybe you loose little velocity in short term, but you are likely better off in long term.
AI is always ready to implement something, or generate code, and make decisions, and it will do whatever you ask it to do. However, to make right decisions you need to understand the problem/context etc etc. And that was always significant portion of work, and you can be little faster with that with AI, but I think that part is still kind of slow but we as industry are in denial about that, and just not doing that part that well anymore.
No, THIS is exactly the kind of BS you get. All that and you didn't answer the question at all. What exactly do you want?
> But maybe, just maybe, think a little about what you are producing, instead of just being a ENTER PRESSING entity. The amount of spaghetti that is being generated is not just an issue from the perspective "oh the code looks horrible to read", but also fundamentally how we build complicated systems, and it becomes bandages over bandages that just sucks and potentially fragile.
Yep, people do think about it. Don't you? Do you not like how others think about it, or do you not like the conclusions they reach? Would you rather they do something differently? Without the BS, let's hear it. What do you want?
Your comment is stating a belief that Anthropic will fail as a business.
AI-pilled folks seem to forget that SWEs are paid to develop _software_, which last time I checked was made from code.
No one merely "solves problems" in a vacuum. You have to engage with a domain, a medium, and the tools of both.
Love this statement, 100% agree.
Though, there's a competing effect: as AI gets better, the amount of skill drops. Maybe the demand for seniors will turn into demand for juniors as AI improves at architecture, and the work shifts towards manual testing.
It sounds like you, like me and probably a lot of us here, are in startup world, but even here I would say the average career is something like four or five years. Most of my peers outside of startup world have worked at the same company the last decade.
I think we're probably the exception still.
Nothing fake about these applicants, they’re just hard to convince.
I'm already remotely prompting Claude through the "senior engineers" where I work. I'm not saying anything, but the company would probably be better off without them. The level of disconnect with the code has effectively turned them into dead weight. They'd be better off replacing them with manual testers.
The question is how long it will take management to notice and decide to do the next round of layoffs.
This is not a good thing.
BigTech headcount growth stalled before LLM. The decade before that, the big employers basically understood that they have to hire from universities and train employees to get to their hiring targets. No one expected the out-of-college junior eng to be net productive in the first year or two. The problem is if you don't need to grow the headcount beyond what the market can already supply you in mid-senior engineers, why do you need to pay for their training?
I cannot believe that companies are still using leetcode. That's just complete idiocy. The game is all about reading and understanding code now. Anyone who is still conducting timed code trivia examinations has completely lost the plot.
Stop cargo-culting your interview process, and use your brains!
So maybe we should try testing for that skill. This is not a hard thing to do.
To be fair, the puzzle problem technical interview itself was always a cargo cult, mimicking Google's process since 2004 at least.
[1] https://www.npr.org/2004/09/14/3916173/google-entices-job-se...
Let's just have a coin flipping tournament.
I do not understand this...Stockholm syndrome...that some programmers seem to have for the idiotic interview system.
There is a century of data and studies that suggest cognitive ability is positively correlated across tasks. Conducting IQ tests for hiring is practically illegal in the US. Leetcode is the closest you get to an IQ test without tripping some laws.
I think you have to let this one go. SAT, LSAT, GRE, ASVAB all correlate well with IQ scores. Leetcode should too, after the interviewee does a few weeks of practice (just like all those other tests).
I mean, you're just making stuff up, but ok.
Leetcode is just one step away from that.
Leetcode is not a general cognitive test, obviously.
> Leetcode is not a general cognitive test, obviously.
What? How's this related to the argument.
If you're saying, like, the Wonderlic test is fine but IQ testing isn't, all you're saying is that the "IQ brand" is problematic. That's wrong, but also it's not saying anything interesting. Call it whatever you want, it's the same business premise.
If you're saying that Leetcode is, like the Wonderlic, a direct proxy for IQ, that's just clearly false.
I hadn't actually thought about it this way, but it makes sense. I'm in my early 50s and hella experienced and talented (if i do say so myself), but I refuse to do any interviews that require me to do any more preparation than researching the company I'm applying to.
It's obviously absurd, and while I almost understand it for a company that doesn't know you, you'll get hit with this stuff when you've been referred internally, by people you worked with in the past.
But there's plenty of people with high intelligence and problem solving that aren't good programmers, so we probably want to try to hone in on that a little bit.
Leetcode is popular because:
1. It gauges problem solving ability and pattern recognition, which are essential to any job, and particularly useful for software engineers.
2. It is language agnostic - most jobs would rather have a strong engineer that doesn't know their particular language/tech stack than a weak engineer that is familiar with the stack.
3. It has objective evaluation criteria (correctness + time/space complexity).
It's certainly not perfect, but I have yet to see an alternative that accomplishes all of the above. The one thing I can see potentially complementing it is the new style of AI-assisted assessment where you are dropped into an unknown codebase, and asked to make fixes/features that are assisted by an AI agent. This solves the language-agnostic issue with pre-AI versions of these interviews, where you had to have memorized specific tech stack features or language syntax in order to accomplish the task. Now AI can take care of that stuff, and the interviewee can focus on the problem solving aspect.
Proof of claim absolutely required here. Leetcode primarily measure's someone's ability to memorize leetcode problems, and secondarily measures their ability to vomit this knowledge up in a stressful situation.
Seriously. There's an entire test-prep industry here. You'd have to be oblivious to not realize that the system has been gamed to hell and back.
Since you are just asserting things, I will assert a simpler explanation: the primary reason Leetcode is popular is because it is cheap. If you have the problem that you have too many applicants and don't want to spend money interviewing them all, you have to come up with an efficient filter that doesn't violate hiring laws.
You don't particularly care if the false negative rate is high, so test of irrelevant trivia is what you do.
In other fields, those things aren't nearly as meaningless and easy to game as they are in ours.
I’m sure the companies know that Leetcode is not a great indicator for likelihood to succeed in the role. If they had a perfect information about people, then would stop interviewing at all and just take the best people who applied.
They don’t have perfect information. The information is highly asymmetric. The companies are just trying to not be efficient and not get burned.
It sucks for candidates. But it makes sense for companies when they thousands of applicants they know effectively nothing about.
Well, no. It rewards ability (and free time) to repeatedly work through problems and memorize the solutions. And it rewards acting skills so you can perform like you're discovering solutions on the fly, that you've actually memorized.
That's all it does.
What you really want to weed out, at least at top-tier companies who can afford to be more selective, is people who have a resume, but are not that great at fundamentals. Most loud complaints seem to be of this nature: guy had N years of experience at previous company/is author of popular software, but couldn't get through basic linked list/recursion/BFS--as if this is not an acceptable bare minimum expectation of a professional in the field.
Often people are too polite to say it out loud, but realistically, that is exactly when it is working as intended.
I think I'm gonna get a stroke reading this. The classic fallacy is the nonsense you're spouting — that there's anything besides the job itself that is relevant to it. You're hiring people for x, so the only thing you care about is their ability to do x. This is obvious.
The perfect test is just hiring someone on the spot and seeing how they perform. We don't do this because it's expensive but obviously it would be the perfect test, measuring exactly what you're hiring for, by definition.
So then any test that goes further and further away from that ideal becomes worse and worse at predicting job performance. The trick is figuring out a good enough test that's still reasonably quick and cheap to do.
Deliberately going out of your way to test your canditates for something unrelated to the job is insanely stupid.
It's essentially just arrogance. Arrogantly asserting that you know for sure your particular random test (Leetcode) is a "random cogintive task" and that it actually is relevant to the particular job.
Again, easiest to see by thinking of the opposite example to before — the worst test possible would of course be something completely unrelated, so idk, having a chef play ping-pong. I'm sure you could convincingly argue it tests something, but why in the world would you not just have him make a dish, since you know, that's what you're hiring him to do? (it's not actually by the way, now that's a classic fallacy — that the job is the mechanical subset of it and not the job as a whole. Soft skills, anyone? sigh).
Another common example of this utter arrogance is thinking that a candidate's performance during a highly stressful, unnatural, and artificial classic interview grilling environment is indicative of their perfomance in the every day feeling-secure-in-their-job state of mind. Oh, look, this fool I'm basically abusing from my position of power is stammering and squirming, must mean he's a good-for-nothing loser! Hah, another fraud found!
So sure, keep putting people in as much stress as possible and asking them how many golf balls fit in an airplane. BTW, I walk out of such interviews immediately. Have fun with your new Leetcode grinder performative actor hires though.
Multiple trillion dollar companies has not been that bad.
It's basically just a grinded leetcode test.
IQ tests ability to learn on the spot, yet leetcode so widely disseminated that people prep for it, defeating the purpose of the IQ test.
Psychologists have said the proper high signal interview has always been a small representative piece of what people are going to be doing in the real job. But nooo, techs seem to be special and well paid enough to invalidate these vast stretches of research right?
Literal psychologists have done the research on this: A good, predictive interview is a small representative test of what people do in the normal job. Only us techbros seem arrogant enough to want to be the exception to decades of research.
The argument that you can use the the artifact of the coding challenge as a starting point for further discussion is perhaps true, but it's like saying that you can use an applicant's resume as a starting point for discussion, once you've filtered out everyone who failed a keyword search.
I wish you were correct. The trend is that nobody reads code anymore, AI writes it and people rubberstamp it with barely a glance (if even that, some companies might have AI rubberstamp it and off it goes into production).
My colleagues use the LLM to do that...
Leetcode could be replaced by learning a made up language, memorizing a huge list of numbers, or reciting an epic poem.
The Leetcode game is mostly memorizing pre-existing solutions and then practicing applying them to lots of variations of the same problem.
The real filter is psychological: will you jump through hoops even when they don't make sense?
Unfortunately that means we may see more of these brain teaser / gauntlet style interviews.
Interviews are so hard
border-radius could have knocked me out of the game, but I decided to keep going. And I'm glad I did.
I’m excited about what this next progression entails. I’m building complex software in months in a home lab that would have required millions in investment just five years ago. In five years I don’t think any of us can say for certain what the industry will look like.
4/5
Have you been able to translate that into a steady income?
compiled languages like C were bemoaned by people because their skill at crafting assembly by hand was suddenly less important.
doesn't ring a bell from the time I went through that transition; people used C and FORTRAN and happily dropped back into handcrafted assembler as needed, and applauded the fully assembler works of some, etc - but nobody (in my recollection, was seriously bemoaning compilers and calling for a return to 100% assembler). similarly with people who were brilliant with arithmetic, or symbolic manipulation, or manual drafting/lettering.
My mother was a computer, she didn't pine for the days of rows of meat computers; I took drafting as part of engineering and worked to assist and eventually replace drafting rooms for cartography- that was a slow rotation out and perhaps had the greatest impact of all the things listed- but people weren't exactly clawing to have their ink stain jobs back.Symbolic manipulation is an interesting one - I recall a general distrust of Monster Group proofs so large they involved software generation and checkers ... but things are still advancing through that same distrust with lean and so on. What I did see is "symbol manipulators" diving into creating automated symbolic algebra suites such as Cayley (now Magma) and still using them today to crack Quantum encryption candidates, etc.
ie. It comes over a bit hyperbolic
If you like thinking, you can keep thinking. AI can't stop you from doing that unless you let it.
Maybe at some point AI will do this better too, and at some point they will just mind read you as to what you're trying to build so you don't even have to be able to verbalize it any more, but we are far from thatm
> The transition we're in includes a substantial disengagement of thought.
While I think you are more correct than not, a cheeky part of me cannot help but think that humanity might be better served if some thoughts were never engaged with in the first place.
1.) I apologize if this is a rather blunt question, but how much of your identity is based on your own perceived (and perhaps exemplified/actualized) intelligence?
I have had a fortunate enough life to have befriended many people who I consider to be far more intelligent than myself. Of these many individuals that I remain in contact with, I have noticed the ones that are the most adamantly opposed to the LLM frenzy, the "death of thought", etc. are the ones that have the strongest attachment/most pride in their own intelligence. I suppose it is a rational reaction, but I think LLMs are revealing hurting a lot of people's egos.
> For those of us who like thinking, this is something to mourn.2.) That statement is what I am most curious about. Do you mind elaborating on what thought there is to mourn? What exactly is being taken away from you? I hope I am not about to come off as condescending, but what is actually preventing you from engaging in deep thought? One is not compelled to use AI outside of their own volition. Even in instances of employer mandates, one is not forced to use AI outside of their occupation.
1. I feel like I have a decent amount of my identity tied up in being "smart". I have always enjoyed learning, have been good at solving problems, and have been able to get out of some pretty difficult circumstances that were definitely slanted against me in terms of being able to find a stable and high paying job through a combination of luck, being born decently smart, and hard work.
2. For my entire life I have been able to work towards or have a job where my purpose is to solve interesting problems and get paid well for it. I have been lucky enough to be in a position where I could paid to sit down and build solutions, understanding every intricate detail of what I made. And now, it seems like the entire industry is just throwing this away. Why engage with deep thought when everyone around is thoroughly convinced that the act of thinking is "last gen" or "going out of style"? If everyone else is wrong, that doesn't change the pressure to just stop thinking and ship 50 commits a day of unread slop. If everyone else is right, why bother thinking? I am just going to lose my job and be stuck doing menial labor until the AGI builds robots that can do my job. Either way I am unhappy. And sure, I do not need to use AI outside of work, but that does not change the existential dread of having the next 30-40 years of my career turned into something that I absolutely hate.
Overall, we have effectively built a machine or a widespread perception of a machine that rewards not thinking and not taking responsibility. Why bother trying to accomplish anything if a machine can do it better than you. I value solving problems, I value understanding, and I value working hard, and at least for me I feel that I may have to start mourning the fact that you used to be able to get paid to do all three. On the bright side, if anyone my age is poised to, by the stupid credentialism of our society, stay in the job market after this, it is me. So either I make a decent amount of money and escape the permanent underclass or all of society is cooked, in which case at least I won't be judged.
Just because someone doesn't believe the same as you, it doesn't mean that they've got a fragile or damaged ego. I, personally, think that people who don't see the death of thought are delusional, and it's got nothing to do with ego.
When someone spends 40 hours per week doing a thing, having the ability, motivation, and pleasure in solving problems they enjoy can and is being taken away. Yes, one can engage in "deep thought" in personal time, if you've got time for that with children, responsibilities, and other leisure activities. Not everyone has time to engage in deep thought enough in free time to compensate for the loss in the workplace.
Been able to finally remove a really painful and bad ORM from a legacy codebase.
Not really, the problem is just changing. Just like C allowed developers to leverage a standard library and a checked type system to create software, AI is allowing developers to leverage english and verifiable specifications to create software. We're all still developing software per a set of requirements at the end of the day.
The varied implementations will always exist and the job is both picking the right requirements to work on, and delivering in a way consistent with its goals.
They're still relevant sometimes. ffmpeg core encode/decode routines are written in multiple different assembly languages. These very same LLMs run on highly optimized code on purpose-designed hardware (!) with plenty of symbolic manipulation to find the optimal execution routines.
3/5
yep
If coding was it, you have a more serious problem than AI
(I'm excluding trivial, hedonistic things from what I enjoy)
FWIW I love not having to spend so much time writing code. I get to focus on solving problems for end users, which is way more fun and rewarding IMO.
It wasn't so much coding that I loved, although I do love that, but being able to build and understand something far greater than myself, and the puzzle of trying to find the right abstractions and tools to make something beautiful.
Boy am I getting tired of reading this sentence.
You make it sound like the only thing that's gone away is the physical act of entering characters -- completely ignoring the fact that working through the problem and wrestling with the code (which included, among other things, typing it) were one and the same. Removing the "writing code" part and expecting the other parts to remain is just as sensible as believing that you can remove a swimmer from the water and expect them to keep their physique.
"Writing code" was one of the most important _mediums_ through which we practiced _deep thought_ about programs. It wasn't just typing.
> FWIW I love not having to spend so much time writing code...
Sounds like maybe software engineering isn't for you? Or rather, wasn't? You're lucky that the "one thing" you don't like about your career was removed. Try and approach those of us who are in the opposite situation with a bit more tact and compassion than "Luckily now is also the best time ever to explore alternative career paths!" What an absurd, tone-deaf thing to say.
There have been many times recently where, by choosing not to have ai generate code that at first glance seemed like it would be repetitive and boring, I have developed much better and more elegant abstractions for what I was trying to do because by working through the code and wrestling with the problem I found a better way to do it.
However, I don’t believe (and never really did believe) that writing code is the only means to understanding how to build good programs. I think best in prose and pictures, so writing requirements docs and thinking through abstractions with component diagrams has been my preferred way to work for years. Maybe I am the lucky one…
Apologies for causing any upset, I really do not wish to cause ill feelings. I want to see our field of software engineering flourish, and if that means trading a screwdriver for a chisel I’m all for it.
This very specialized audio DSP programming that was in short supply is now something almost anyone can do.
You need the synth domain knowledge but the software programming is solved for all intensive purposes.
The DSP programmer of course will be the best firmware vibe coder but they surely were better off when they had this rare skill vs everyone now having that skill.
One of my favorites; pardon the pedantry: "for all intents and purposes". :)
But I googled this FM-1 thing and watched some Youtube videos and it seems pretty cool! I might get one to play around with for the fun of it.
And I doubt I'm alone. So maybe the DSP programmers are worse off, or maybe their market is about to explode because it's so much more accessible, and there will be all kinds of new niches and opportunities for their skillset in this much larger market.
Maybe not, I have no idea, but my own reaction to seeing this was interesting, so I figured I'd share.
But I dunno, I'm very ambivalent about it.
I feel very negatively about the rise of AI for many reasons, but personal economic prospects is not one of those reasons.
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.
of course, I'll still be doing systems. maybe from my cabin in the woods, hiding from the machines, but I'm in it for the love of the game.
In the 80's, when I was about to start a computer science degree, a friend said his father thought it was a dead end because the computer would be able to program itself soon. This was the era when 4GLs were beginning to be a thing.
So much of the job is just helping the business people figure out what they want and trying to regularise their ridiculous arcane manual processes.
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 :(So someone invests time and energy into figuring out good UX, sensible architecture, and releases a good product. Then a swarm of clones come about and depreciate the value nearly instantly. Who wants to invest in making good products?
If you’ve used AI extensively you realize how easy it is to copy relative to create.
2. Businesses still want to offload cognitive effort elsewhere (such as software vendors), if that software is not what the business does. Copying mature software with your AI is a terrible business plan, and wastes your money and time. And I'm not going to choose one of the swarms of clones, why would I? Your view is like saying why would anyone pay $$$ for a well made purse when there are thousands of knockoffs that look exactly the same?
3. Software that touches the real world will never be exhausted, because the detail and complexity of the real world is unbounded and constantly changing.
> Let us now assume, for the sake of argument, that these machines are a genuine possibility, and look at the consequences of constructing them. To do so would of course meet with great opposition, unless we have advanced greatly in religious toleration from the days of Galileo. There would be great opposition from the intellectuals who were afraid of being put out of a job. It is probable though that the intellectuals would be mistaken about this. There would be plenty to do, trying to understand what the machines were trying to say, i.e. in trying to keep one’s intelligence up to the standard set by the machines, for it seems probable that once the machine thinking method had started, it would not take long to outstrip our feeble powers. There would be no question of the machines dying, and they would be able to converse with each other to sharpen their wits. At some stage therefore we should have to expect the machines to take control, in the way that is mentioned in Samuel Butler’s “Erewhon”. "Intelligent Machinery, A Heretical Theory" (1951), from a BBC radio discussion programme, The ’51 Society.
> we find ourselves almost awestruck at the vast development of the mechanical world, at the gigantic strides with which it has advanced in comparison with the slow progress of the animal and vegetable kingdom. We shall find it impossible to refrain from asking ourselves what the end of this mighty movement is to be
> What sort of creature man’s next successor in the supremacy of the earth is likely to be. We have often heard this debated; but it appears to us that we are ourselves creating our own successors; we are daily adding to the beauty and delicacy of their physical organisation; we are daily giving them greater power and supplying by all sorts of ingenious contrivances that self-regulating, self-acting power which will be to them what intellect has been to the human race. In the course of ages we shall find ourselves the inferior race. Inferior in power, inferior in that moral quality of self-control, we shall look up to them as the acme of all that the best and wisest man can ever dare to aim at. No evil passions, no jealousy, no avarice, no impure desires will disturb the serene might of those glorious creatures.
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.
One of the biggest uses of vibe-coding that I've seen is non-technical users creating throw-away tools to help them solve their current problem.
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).
And, what do you mean by "AI can't innovate"? I suspect that for any definition you pick, either most humans also can't innovate, or examples of AI innovation can be found. And this is only going to get better.
See Chris Lattner's observations about compiler written by Claude: https://www.modular.com/blog/the-claude-c-compiler-what-it-r...
If you're going to discuss this, start with a definition of innovating.
You should stop coding then. Just use Claude.
Talk to customers: not dev
Write specifications: could be dev at least in part, but I don't see why others can't be more productive here
Generate code: AI + light human oversight
Build: CPU (not dev)
Deploy: AI (not dev)
Secure: AI + human oversight
Market: sales (not dev)
Sell: sales (not dev)
Support: support (not dev)
Monitor: AI (not dev anyway)
Be on-call: I guess a human should pick up the phone and then do what? AI + human at best.
Handle incidents: depending on the incident, AI + humans (also not dev)
Track bugs: Well, you got me.
So we are there to do the administration and handle unforeseen consequences AKA support and incident response, which is, sorry to belabour the point, not dev. Just a part of it and the not so fun part as well.
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.
SWE's have to guide the AI, look at all those AI PR's, many of them make very bad assumptions.
As a result I decided to start using those LLMs myself, to see what they could do and how quickly they would make me obsolete. Two months later, I feel a lot less worried. Yeah they're really good for some things and they do save me a lot of time in some cases, but I wouldn't trust them to develop a complex application from the ground up without oversight. If it's a one-off prototype thing then maybe, but for a serious long-lived project it's going to be utter chaos and confusion.
One of the reasons the bots are so good at pure coding is that code is designed to be machine-friendly by definition, and the feedback loops are extremely short and cheap. Oh you forgot to add an #include? Read the compiler's error message and fix it. Takes 2s. I suspect that's also true for the Mathematical proof work to some extent, your Lean either checks or it doesn't. As soon as problems become more organic and less immediately testable, you can see models losing their footing. When there isn't a clear test to decide between A and B, the models easily panic, loop, overthink, underthink, miss alternatives etc...
Of course it may change. Maybe next year Opus 15.5 will truly outrank me. But there's still a long way to go IMO.
So many executives have turned all the safeties off and given over control of their business to a probabilistic system and ignored every engineer who said its dangerous and risky. The engineers will be the ones held accountable though, because since AI is "so effective" it must be operator error
Second point should be obvious to anyone actually building something even slightly new/complex.
2) I think u might be right about brute force - but probably some methods/tools will come along first - and I don't think they will solve the problem though.
I think SWE is actually very safe.
We're going to need fewer 'JS coders' and technically we could 'save' a few SWE jobs - but - given the $ being made, businesses will want to expand, and so 'Jevon's Paradox' and I think SWEs will have jobs and probably even the JS jocks as well.
Ofc unless you call some data modelling “architect” but I’m sure AI is fine for that. Guess how I know.
This does not match my experience. At work I have AI write architecture docs for complex features based on requirements that the product team collects. When staff engineers review those docs, in the overwhelming majority of cases the only issues they can find can be characterized as nits or bike-shedding. In contrast, AI can find problems and even serious gaps in architectures designed by the most seasoned engineers on the team (because those engineers have been doing their best to resist using AI).
So I think the whole "AI can write good code but it cannot design architecture" is just cope. It's where the goal posts have been moved to after it became impossible to deny that AI can actually write good code. Next up it will be "AI can write good code and design good architecture, but it has no taste". Indeed we're seeing various of that already.
You still need someone at the wheel with a strong sense of where the architecture should go. If you just let AI drive, it goes in circles forever.
Just had this experience at work. I tasked a mid-level engineer to architect a brand new complex system with AI assistance and he spent a month burning tokens trying to get everything specified. Between AI going down irrelevant rabbit holes and him not being assertive enough over the AI, it didn't work. After a month, there were still tons of open questions, undecided workflows, etc. I wanted to try this as an experiment, and to give him the opportunity, but it didn't work. And this person is not at all incompetent, just doesn't have enough experience in big-picture system design.
I reassigned a very senior engineer to take over the project on Monday and in a few days (writing this on a Thursday night) the design is done and implementation is well under way.
Ai is not a magic silver bullet. It's a wild horse and you need a master horseman to tame it.
For my entirely relationship with him, my tech friends all talked about how his job was basically automated and planes will fly themselves soon.
Welp, turns out our jobs were made obsolete first.
I'm not scared for the future of software engineers and computer scientists.
I can think of several bigger moments in the last few months alone
My worst fear is that I will have to do an absurd job where my brain rots under people with less skills and ethics but better at playing the new game.
It's the boot camp/degree/whatever to get the paycheck but never enjoyed the problem solving or learning aspects...
Coming from the service industry, yeah there's some long stressful days doing software development but those barely held a candle to average weekends / holidays working at restaurants and cafes.
Then the whole boot camp thing happened, where it's like sure, I guess since you spent 4 weeks learning just React you're worth as much as someone whose been doing it for a decade? I figured that would have been the end of inflated software developer salaries.
Now we're here.
They certainly did not. LLMs are way worse than a competent human programmer.
On top of that, we're not hiring less people, we're just building (slightly, the speedup isn't consistent across all parts of the workflow) more products
There's obviously still a requirement that people have a lot of skill and knowledge to produce good software, and I'm not sure that's going to go away.
The tricky part is you have to price your offering well below what your potential customers think it will cost to vibe code an equivalent.
More prosperity than you've ever had.
I grew up in a third world country, so I can say first-hand that the internet has helped the average person around here gain opportunity and open doors to the possibility of prosperity.
A dystopian vision that keeps popping into my head is from the movie WALL-E, where the robots are running everything and the humans are overweight blobs gliding around on recliners with entertainment pumped into their eyeballs and endless soda refills. Is that what a world of "abundance" but no meaningful work, looks like?
There's meaningful work everywhere you look, WALL-E is nowhere near our reality today. Also, why the hell would you choose to be fat in a "world of abundance"??
Also people still have dreams, many of which are related to being skilled at something, which will always be meaningful.
YMMV I guess.
Don't oversell it.
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.
Not sure what’s going to happen but it’s not pretty. I have been pushing my wife to sell our house and downsize but she doesn’t agree. I was telling her that once that happens no one is going to buy our house even at a 50% discount.
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.
In a way it reflects how repetitive our industry is. We train a model based on the github projects and much smaller expert data, yet the model is sufficient to solve many of our current prolbems.
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.
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.
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.”
Not everyone gets to work on the most interesting engineering problems, I think most of us felt more like glorified digital plumbers. The money was too good to pass up that CRUD work but I can't say it was very fulfilling, I'm glad a machine can do that drudgery for me now.
If you feel this way this speaks volumes towards the value your work provides.
That’s in the corporate world. Privately, the big sadness is that one can no longer be a solo dev without either renting inference or laying down serious capital to run it yourself. The era of John Carmacks sitting in front of a $10k rigs, simply to be able to do their job, has swung back into fashion.
So much of what I do every day are non-coding jobs that aren't actually that easy to do with AI (of course that's not technically true but as a practical matter corporate America is probably not going to change all that fast, we've had lots of automation abilities for years that they still don't embrace with any great amount of success).
But what about the team of Genpact developers I have in Hyderbad & Bengalaru? They're coders, and I know already that I can take what I give them and run it through Claude Code myself and get results 100x faster, with better quality to boot. With less of my time needed to review & provide feedback. These guys, love 'em, but they're fucked. I've been trying to help them level up, but they're mostly freshers and it is a steep climb.
Luckily our senior management is still slow-walking our foray into LLM coding, but I know my manager already sees the writing on the wall (though he's more worried about his own job than ours).
Any type of cuisine was served around campus for breakfast, lunch and dinner, and it was high quality. If I wanted dessert, there was entire shops (not one but many) serving free handcrafted desserts. If I wanted my laundry done, someone could handle that. If I wanted snacks, each floor of my office had its own little mini bodega.
All of that, and we were being paid a very handsome amount compared to others outside of tech. What other professions can have such a nice and mostly risk-free life, and get so highly compensated compared to the rest? Software engineering was always a case of limited supply in a world of high demand.
Of course now there are more pictures taken than ever. Millions were displaced from their jobs but billions now benefit. I suspect the same will happen with software and and LLMs. I can argue that the loss of the craft of analog photography is indeed a loss but almost nobody cares. I suspect that the loss of software writing skill will suffer a similar fate.
Keep in mind that LLMs are just the hot product of the here and now. They will enable us to now rapidly construct a variety of intelligence services.
If human intelligence doesn't hold value we won't train children for it so aggressively. And with lower demand for education will come a decline in all matters of society.
This is an existential threat to civilization.
It really isn’t. Not even remotely. Trusting the word of mega corporations that convert this rhetoric to cash is perilous at least on a personal level.
Every health care provider I've seen in the last year uses AI for transcription and synopsis, at the minimum.
That's just the regular folk. AI is cutting deep into science and research. Schools are overwhelmed by its use by students.
And frankly, from what I've seen it does a much better job than _most_ humans at all of these tasks. Let's not forget how regrettably disappointing human mediocrity really is.
Besides, what I think is that AI putting us out of work is destined to be the least of our concerns; we are going to experience far worse thanks to our failure to curb carbon emissions and ecosystem destruction.
And this is still the early days. LLMs could plateau in capability at this moment in time and still have a great deal of opportunity to penetrate markets currently reliant on human intelligence.
Think of electricians, plumbers, carpenters, mechanics, etc. People can and do attempt and often complete that work themselves, but larger projects, professional projects, and people that don't have the time nor expertise but want a good job done pay professionals to do the work. The AI is the toolset, and experience in using the tool and knowing where and how it works best and the tricks to make it work effectively will be the real distinction, between a layman and professional.
There will also be people that are more specifically on the software engineering side, where they might be equivalent to a contractor or an architect depending on size and complexity and how much is design and how much is assembly, so it won't just be people assembling stuff from AI designs.
All that's happening is that we'll get some stratification of roles by what different positions are good at, and we might get some actual certifications that mean something, and while the total number of professional programmers might go down, there will still be a need for them at all skill levels, and the general public will dabble in it much more often.
There's going to be a shake up and a rough time for surplus programmers, but just as there was a surplus of woodworkers that had hard times when the assembly line was introduced and popularized, it will normalize over time. I suggest people either lean into their tooling a lot to learn how to use it well enough to be those that survive that culling, or look into related fields that won't be eaten quite as much which they can inch towards.
I don’t expect all SWEs will go away, but maybe 80% of us will. Fewer and fewer experts will be needed to get increasing productivity from ever more independent and intelligent agents.
This is several years away though. In the meantime I expect we’ll all be very busy fixing bugs and security holes.
The gravy train is just starting
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”
Surely, the invention and application of the technology was that moment, not the IPO of a single startup using it.
"Gravy train" is defined as an "easy, lucrative job that makes money with little effort".
I certainly would not characterize SWE as remotely that. I'm sure you didn't intend it, but it's that kind of anti-labor speak that rationalizes human replacement with tech.
It frames workers as people who are somehow taking advantage of corporations or "the system". That people casually engage in this language speaks to the success of corporate anti-labor campaigns.
2/5
Openai gpt 2.0 was the massive moment, each incremental model has been pretty extraordinary to experience...
Listing on NASDAQ... who cares?
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.
I agree, but I think a lot are realizing that's not what they signed up for. They actually don't want to solve problems in general, they want to solve code problems. Without that the job is meaningless for them.
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.