Get wrecked. The actual reason bro is not worried is in the right column:

> I am an EIR at Balderton Capital and principal of my own eponymous consulting business.

> I bring an uncommon perspective to enterprise software, having more than ten years’ experience in each of the CEO, CMO, and independent director roles in companies from zero to over $1B in revenues.

First, what the hell is an EIR.

Second, the fact that you are one at some Bertie-Wooster-ass venture capital firm means that you could probably retire tomorrow, if not necessarily in the manner to which you are accustomed

So yes, must be nice

> there is always, always more work yet to do

And they always, always forget that it's not about "work", it's about whether a particular person will be able to contribute work that someone is willing to pay for. It's definitely NOT true that there'll always be more paid work to do that can be done by a particular person.

But this is what you get when these authors are wondering if something is good for "the economy" instead of thinking about actual people.

i appreciate the sentiment to a certain extent - its not going away, skate to where the puck is if you care to do so. but the writing is repetitive and theres an entire repeated paragraph (bullet to paragraph form). there are also lots of things to be worried about even for the most seasoned individuals in terms of half decade increments conservatively. assuming large parts of swe become commoditized in the form of paying a handful of frontier model providers more and more of the share of what was once swe wages, the high end is what survives. high context fox-like (a la terrence tao's foxes and hedgehogs) are guiding ai to build - and then they are eventually displaced as well. extreme societal pain seems like its on the horizon assuming we dont have some incredibly unlikely massive mobilization towards post-work post-scarcity thinking with active social safety nets. economic diffusion probably means this is a little further away than we think, but time moves pretty damn fast.

An (ex-) Senior VP at Salesforce is not worried about running out of work.

thx lol -- why is this on the front page?

The writing is on the wall, but what it spells we don't yet know. One thing that is virtually certain is that tomorrow's world of software engineering will be very different than today. Thinking about and preparing for this world is something we need to do.

I take the negative comments here as expressions of anxiety about the future - we are, after all, this industry's auto workers in what may be the Rust Belt.

> The real move for the autoworker was sideways, not upward: industrial maintenance, tool and die work, welding, industrial electrical work, construction trades, trucking, or logistics.

But in an AI post-work future, all the sideways moves have also been taken over by AI and robots. After all, “knowledge work” as a discipline will not be there, right? Whether I can write code, manage teams or copywrite. All of them automated.

When the complexity vs cost of automation tips in the favor of humans, that’s where I’ll have to skill to. You said it, trucking, welding, … That I have a PhD in knowledge work is just worthless paper now.

I like the horse analogy.. we will always find a way.

"Retirement aged man not concerned about finding work"

> Aggressively learn AI.

Unless the author is talking about learning how transformer architectures work, and I don't think they are (and if they are, it won't help the vast majority of people anyway) this is the dumbest advice I keep seeing.

You don't have to "learn AI". "Learning AI" will not be a moat, for anyone. The power of "AI" is that you prompt it in plain language. And it just goes and does the thing. Using AI is not really a skill. It arguably was a little bit when the models were a lot dumber, but now it isn't.

This "transition" is going to be way worse and way more disruptive than even people who think they are thinking about this problem assume.

When is AI going to take over the executive positions? I'm sure they can do a much better job than these guys.

So many things wrong with this article.

>> The popular horse-switching fantasy answer is retraining. “Go back to school and become an engineer.” In theory, yes. In practice, rarely. The jump from an assembly-line worker to an engineer requires years of schooling and a different educational foundation.

Sure...and after "years of schooling" that work will also get taken by AI, since learning is accelerating. Remember 6yrs ago they told laid off people to learn to code? Then remember 3yrs ago they said to learn to prompt engineer. Unfortunately the tech moves faster than retraining for many.

>> So many things that we could do to help our customers.

Author assumes the customer is still in good shape. Not a great assumption, the value chain is being squeezed and disintermediated.

>> Which is why the idea that we’re somehow going to run out of work strikes me as absurd. It feels like a theory written by people who haven’t actually spent much time doing the work in the first place — serving customers, building products, and running businesses. There is always more that could be done.

Sure, there is always work. Not sure what the ROI is on the work though, is it worth paying someone to do? If so, why wasnt it done before?

Will swe's be squeezed; yes. But I don't think everything will just be magically done by these models. Right now the wheels are completely off the wagon as we see more and more vibe coded apps going live with fatal security vulnerabilities, privacy issues. The act of putting pen to paper, will change, the positions will change, but I don't think these models are a silver bullet.

Nothing has been so simple until now, and it seems strange that we just get to a certain point and then all of our problems are now just solved, completely. From my experience until now, at my current start-up, it has reduced our need to hire a tad, but not too much. However, I've also seen early stage start ups needing to hire because they started out building a product, and it became too much to handle, it is anectodal and current, I'd just find it strange that we just end up automating ourselves away, my own role has sort of turned into an AI enablement for the rest of start up, mostly C-level, business, pretty much everyone else than swe's. There is potential but mixed success for now. Agent's a good enough to build something that works, but not good enough to build the right solution.

I had a guy that ended up building a local dashboard in perl (the only thing claude could find on his mac) and wanted to distribute it to his colleagues. Engineers sometimes forget that normal people don't usually work in the unknown, they will solve problems in any way they known, in this case a airdropped folder of perl code sent to each other.

I’m not worried about running out of work. I’m worried about running out of paid work.

Somewhat buried in the post — “focus”.

The way people use AI is the opposite of focus. It’s throw as much as you can against the wall because it is fast and cheap and possible. It is peanut buttering. Companies today mandate AI use so indiscriminately that you might as well call it a comparative disadvantage. It’s not that the AI is bad, but that people haven’t figured out that the core competency of an organization is focus and coordination to achieve a goal, and that victory is external — users, customers. But AI is used to unfocus, to spread, and to meet internal goals - build more, etc. The challenge was never writing more code or creating more content (all of which is ultimately a long tail of debt that needs to be cleaned up and managed by someone else), which can be done cheaply enough with other paths. It was figuring out what is worth doing, and aligning everyone around that. So in a sense, I welcome company AI mandates today because they are so misdirected as to make “doing things they inefficient way they were done before” a relative advantage.