News for hackers. Stuff that matters.
Re:The staggering impact of IT systems gone wrong by dijit on Wednesday October 21, 2015 @07:20AM (#10424723)
But there is a profession dedicated to preventing these kinds of failures: Systems Administrators.

Proper infrastructure engineers (or "site reliability engineers" as google now calls them) are key for helping architect highly available systems like this; Yet the trend seems to be forcing software engineers follow tutorials from google on setting up key pieces of infrastructure nowadays.

Edit: it's ettiquite to say why you're going to downvote someone, if what I said wasn't relevant please let me know.

Re:The staggering impact of IT systems gone wrong by falcolas on Wednesday October 21, 2015 @08:53AM (#10425048)
Haven't you heard? With Amazon and Heroku and Google, SREs are obsolete! Your developers can manage their own infrastructure. /s

Our own company learned the truth about requiring an operations team the easy way - they hired some and their reliability went up. Outages started being handled before it impacted customers.

It's been fun watching the volume of "Oh Shit" emails dropping precipitously.

Re:The staggering impact of IT systems gone wrong by mannykannot on Wednesday October 21, 2015 @09:57AM (#10425413)
I did not downvote you, but I disagree with your premise. Systems administration is only part of the problem, and only in some cases. A non-inclusive list of other causes include failing to understand the intended purpose of a system and the environment it is to operate in, and losing control of the design.
Re:The staggering impact of IT systems gone wrong by dijit on Wednesday October 21, 2015 @10:31AM (#10425634)
I would agree with what you said, but I would argue that the points you raised still fall into the realm of systems administration.

Identifying scope and purpose, and it's impact and documenting the design are just some of the things an platform operations team is -supposed- to take care of.

Re:The staggering impact of IT systems gone wrong by mannykannot on Wednesday October 21, 2015 @10:40AM (#10425709)
If you expand the definition of systems administration to include everything, it doesn't get you any closer to a solution.

The largest problems of development have nothing to do with administering anything (edit: for example, bad design often results from bad design decisions that are neither prevented nor fixed by seeing that the required documents have been written.) The idea that Winslow Taylor's principles can solve these problems is a fallacy - a commonly held one, but a fallacy nonetheless.