Quote Originally Posted by NanaWiloh View Post
OP claiming to work on Servers does not mean crap!! You are not the one handling SE servers. You dont know their server infrastructure your making blind anger filled guesses as to what the problem is, secondly any joe blow can claim to too work on servers so your wasting your breathe on that one.
Whoa. Calm down. Take a breath. I’m skeptical of some of the OP’s claims as well, but in your rush to post your outrage you’re one run-on or typo from a heart attack.

No matter what, remember that regardless of what SE’s current infrastructure is, there are industry standards. If they (and they certainly did) chose to ignore the collective wisdom of the DevOps community, that’s on them. Thankfully, there are larger businesses with older tech who are still managing to be dragged kicking and screaming into the 21st century. They can do this because the industry has put a massive amount of focus into providing layers of abstraction that can make the client, the server, or both completely blind to the fact that they’re being dynamically load-balanced and elastically scaled.

I can tell you from experience, the hardest part isn’t the technology. Once you get the right stuff approved for the job, it’s not too bad to implement. Not trivial, and there’s a reason DevOps professionals get paid well (Unlike most software developers. Holy crap do we get hosed by comparison). But seriously, the hardest part is convincing management that it’s time to catch up and do the right thing. Gaping security vulnerability? “They probably won’t hack us.” Critical performance instability? “We can just reboot every night until we decide to figure it out.” That’s what holds the dev and infrastructure teams back. Not that we’re being asked to solve unsolvable problems.