Live data from Hacker News

Knightmare: A DevOps Cautionary Tale (2014)

dougseven.com

291–294 of 294 posts

Re: Knightmare: A DevOps Cautionary Tale (2014)

#291
post #277

Earlier quoted context omitted.

[flagged]

Hey, can you please review the site guidelines and stick to them when posting here? We have to ban accounts that won't. https://news.ycombinator.com/newsguidelines.html

Yes.

I expect that the comment above describing jobs in finance as a "waste of life", with no other content is also unacceptable.

Re: Knightmare: A DevOps Cautionary Tale (2014)

#293
post #277

Earlier quoted context omitted.

Hey, can you please review the site guidelines and stick to them when posting here? We have to ban accounts that won't. https://news.ycombinator.com/newsguidelines.html

Yes. I expect that the comment above describing jobs in finance as a "waste of life", with no other content is also unacceptable.

It sounds like it! but I didn't see that one.

Re: Knightmare: A DevOps Cautionary Tale (2014)

#294
post #26

I'm not sure how automated deployments would have solved this problem. In fact, if anything, it would have magnified the impact and fallout of the problem. Substitute "a developer forgot to upload the code to one of the servers" for "the deployment agent errored while downloading the new binary/code onto the server and a bug in the agent prevented the error from being surfaced." Now you have the same failure mode, an…

> The blame here lies squarely with the developers--the code was written in a non-backwards-compatible way. The blame completely lies with the risk management team. The market knew there was a terrible problem, Knight knew there was a problem, yet it took 45 minutes of trying various hotfixes before they ceased trading. Either because they didn't have a kill switch, or because no one was empowered to pull the kill sw…

[deleted]
Post reply on HN