this post was submitted on 30 Jan 2024
778 points (98.3% liked)
Technology
73876 readers
3382 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- 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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- 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
Until it becomes obsolete, unsupportable, the crux of your operation, and/or the basis for all of your decisions π¬
(Yes, I read the article, itβs just the signs, but yes, the above still applies!)
COBOL has entered the chat
e: good for legacy employment though. A relative of mine is a Z80 programmer by trade, and he can effectively walk into a job because the talent pool is so small now. Granted - the wages are never great but never poor, and the role is maintenance and troubleshooting rather than being on the leading edge of development - but it's a job for life.
π₯²
Not to mention when you want to change the entire system it becomes a huge operation and problem.
Massive risk to that change too.
So many people don't understand how risk informs everything a business does.
What cost is there to a given system being down for one hour? A day? Any regulations around it?
Often it's better to pay a known quantity up front than risk potential outages where you can't predict all the downstream affects.
I'd consider those various states of not working. So... Don't fix it if it's not broken!