74
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Jul 2024
74 points (96.2% liked)
Ask Lemmy
25325 readers
1128 users here now
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
founded 1 year ago
MODERATORS
Probably the same type of shit that cobol is. Some absolutely ancient system that they will never properly update because a 400k a year programmer is cheaper then doing so.
If it was only one shitty ancient system it would be one thing. For the company I work for it's about 10 big interconnected mainframe systems with hundreds of non-mainframe systems cobbled together around them. They've been in place since the 80s, but you can trace their business logic back to the 50s and 60s. They start at cataloging all our parts and get into purchasing components from suppliers, describing the products we assemble, managing the supply chains for our factories, order management from our customers, etc.
Replacing it all will be massive chore, but it's becoming more and more clear that we need to. At the end of the day, capturing and understanding data in them takes so much skill that we have entire departments dedicated to being an interface between the actual users and the mainframe. The business rules might have worked before the products we build contained electronic controls, but everything is starting to implode now that "parts" also includes software. This has resulted in manual workaround on top of manual workaround.