this post was submitted on 30 Jan 2024
844 points (98.2% liked)
Technology
59436 readers
3631 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 another!
- 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
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The secret is to develop your software, then fire all the developers. Then it never changes again!
Come to think of it keeping developers on staff, and familiar with the codebase enough to debug it efficiently, almost guarantees they’re gonna be adding new features. “Well we’ve got this talent sitting around …” and then it’s new features and ….
I mean I guess this is evidence they’ve managed to isolate themselves from dependencies they don’t control. It’s the external dependencies updating and losing support that causes at least the minimum of codebase maintenance.
The fact they’ve stayed on this older platform indicates they’ve managed to avoid that constant upgrading. Because if any part of the system has to upgrade, it tends to pull the rest of the system with it.
This gem requires this version of ruby requires this operating system etc.
Or maybe they’ve isolated the parts really well and this is just some window3.11 container that’s one of a hundred services.
I’d love to go back to tech without the constant insomnia and panic attacks.