I've shortened the title just a bit due to the character limit. 72 hours of production downtime is /insane/ to think about and with such a brass attitude comin

I've shortened the title just a bit due to the character limit. 72 hours of production downtime is /insane/ to think about and with such a brass attitude coming from the team as well.... I'd be inclined to go to the board and ask for additional funding to start a new team/begin knowledge transfer ASAP and start winding down the old team. I'd be curious to know why the CTO's isn't being grilled about the downtime and if they even have a CAPA process to prevent this from happening again? Additionally, one of the commenters in the thread also points out just how important devops as a /culture/ is compared to just treating it as something to be bolted on at a later point in the organization life. I've worked with too many devs that seem to think their involvement ends when they throw the code over the proverbial "devops fence".