1. 8

An old but good article on a DevOps disaster that led to the bankruptcy of a financial company.

  1.  

  2. 4

    I can understand how any of these things happen, but I do not understand why a development team would re-use configuration settings and give it a completely new meaning. That just sounds like asking for trouble. I really wonder what led to that decision.

    1. 1

      Most likely some company policy on facilitating code reuse, or maybe adding a new flag would’ve been too much work?

      Either way, this is a process failure on every level. It’s a fascinating read. I was talking to a friend about it earlier today and when I checked here I just saw it was posted 3 years ago, so a lot of new people could see it.

    Stories with similar links:

    1. Knightmare: A DevOps Cautionary Tale via joshuacc 4 years ago | 15 points | 7 comments