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.
I've also seen non-technical folks in the corporate and government worlds glom onto vibe coding, only to start flailing like they were caught in a rip current when the underlying technical debt is too strong, even with strong and capable models.
For a certain type of engineer who enjoys really arcane technical problems, yeah, the gravy train may be over, or at least will involve a lot more machines than it used to, as Alan Turing predicted about "mechanical work" becoming a "drudge."[0]
And I think Big Tech is for the foreseeable future a sink for capital in the form of specialized hardware rather than human capital.
[0]https://en.wikiquote.org/wiki/Alan_Turing#Quotes