News for hackers. Stuff that matters.
Re:Chaos Monkey Guide for Engineers by karlkatzke on Saturday February 16, 2019 @10:27PM (#19182521)
No. That’s entirely not the way it works. Chaos Engineering works in companies with significant scale and sufficient maturity, and the purpose is to discover design or implementation failures in distributed systems before they happen during big rushes where you’re hopefully making lots of profit.

If you lack sufficient maturity or you are not large enough, you will actually lose benefits if you try to implement chaos engineering. It’s like teaching a toddler to use a propane torch. You just don’t do it, or everything you love in the world will burn.

Re:Chaos Monkey Guide for Engineers by karlkatzke on Saturday February 16, 2019 @10:39PM (#19182549)
Self reply to realize that I shouldn’t lecture my grandma on how to suck eggs.
Re:Chaos Monkey Guide for Engineers by jedberg on Sunday February 17, 2019 @12:18AM (#19182797)
Maybe I should have added a disclaimer with the :) at the end.

Thanks for the laugh though. Your phrasing was awesome.

Re:Chaos Monkey Guide for Engineers by empath75 on Sunday February 17, 2019 @10:22AM (#19184863)
I’m telling you from experience that’s wrong. We did it at a project with just 15 or 20 developers, starting from day one of development. Literally the first thing we installed was chaos monkey before doing anything else, even before getting Jenkins running.