Raw LLM Responses

I sell no-code SaaS now. I get manufacturing, having sold into it in the past. Sounds like legacy applications. I will never understand homegrown applications running critical functions, those applications can't scale, a select few know it, the shit sits in folders or server location and little documentation, plus as in your scenario when the developers leave than what. The typical silos of applications, lack of automation. Most likely running stuff on a mainframe, i-series as400. I can't believe how manufacturing companies are stuck running legacy apps. I wouldn't be surprised to hear the use of an old JD Edwards version (horrid scheduling functionality) or an older Infor or SAP version of ERP. I used to sell Enterprise workload automation (batch scheduling automation), and we plugged into the entire tech stack. The silos amazed me, the bigger the company the bigger the mess. Let's say you have a mixed OS environment Windows, Linux/Unix, your running jobs and processes. Two teams where most don't know the other side. Using Windows Task scheduler, Cron scheduler, or basic native scheduling in an application. JD Edwards scheduling blows. I don't get why companies don't redece these silos and centralize into a single platform. So say a job or process doesn't run it takes down the entire run process and there is lack of notification, triage, shit log info etc. All hands on deck to figure out what went wrong and why. My favorite is having to set time buffers between job run times. This isn't the 80's or 90's people. There is software to automate and reduce silos, make it easier for your IT teams. I have stories like yoursof systems going down and costing $$$$. FIS Global (huge company) was a client of mine. They didn't want to pay for training for a couple users of our solution (which was powering job processes for clients, Honda website loan apps for example). The admin accidentally takes down the prod scheduling environment, it blows up clients processes for h