4 ms·
I’d guess a long time! The way we engineers build systems is to have a solid core and then a lot of fancy cruft to handle the constant stream of inevitable cha
by reacharavindh 4y ago
I’d guess a long time!
The way we engineers build systems is to have a solid core and then a lot of fancy cruft to handle the constant stream of inevitable changes that bring in new features or update stuff. Take the changes away by removing people who’d roll them out, and you have the core running as it was designed to do.
I believe when the remaining engineers or the new ones(if they will be..) start rolling out changes is when shit will break and make the whole thing wildly unpredictable.
- yardie 4y agoThis might be true for internal applications. Once you plug anything into the Internet all bets are off. Who's auditing for vulnerabilities, patching, rollbacks. Changes aren't made on a whim. There is either a business, strategic, or security need for them. And it's that last one where everyone is worried. No system is perfect. It's how you respond to them that matters and if no human is in the loop what sort of response can you expect?