521
Tech's Dumbest Mistake: Why Firing Programmers for AI Will Destroy Everything
(defragzone.substack.com)
this post was submitted on 11 Feb 2025
521 points (96.4% liked)
Technology
62073 readers
5024 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't know. I look at it like firing all your construction contractors after built out all your stores in a city. You might need some construction trades to maintain your stores and your might need to relocate a store every once in a while, but you don't need the same construction staff on had as you did with the initial build out.
In my experience, you actually need more people to maintain and extend existing software compared to the initial build out.
Usually because of scalability concerns, increasing complexity of the system and technical debt coming due.
Most extension today is enshitification. We've also seen major platforms scale to the size of Earth.
If you're only going to maintain and don't have a plan on adding features outside of duct taping AI to the software, what use is it maintaining a dev team at the size you needed it to be when creating new code?
While true, that is a weak analogy. Software rots and needs constant attention of competent people or shit stacks.
I'm not saying you can fire everyone, but the maintenance team doesn't need to be the size of the development team if the goal is to only maintain features.
It works for a while. Keep a few seniors and everything will be fine. Then you want new features and that's when shit hits the fan. Want me to add a few buttons? 1 month because I have to study all the random shit that was generated last week.
Twitter and Tumblr are operating on skeleton crews but are able to make changes.
Craigslist is still around even though it hasn't changed much since the '90's.
There is an entire industry of companies that buy old MMO'S and maintain them at a low cost for a few remaining players.
Southwest Airlines still runs ticketing on a Windows 95 server.
I think you'll see more companies accept managed decline as a business strategy.
Twitter, Tumblr, Craigslist: those web sites are feature complete and require low maintenance.
Southwest Airlines: good for them, but if the servers have issues, they will lose billions while trying frantically to find the retired guy who maintained that monster.