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.
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.