At first blush, it is a good and maybe even great article. But there's a serious problem that the author is writing about his very small sample of experience a

At first blush, it is a good and maybe even great article. But there's a serious problem that the author is writing about his very small sample of experience and claiming it applies broadly. First, he sets up a false dichotomy between the (good) lean startup and the (bad) regulated enterprise. Because his enterprise experience was in a regulated industry, BTW regulated for Very Good Reasons. But actually most enterprises are not regulated, and don't just take a cautionary approach because the government bogeyman told them to and it's out of their control -- with very strong implication they would not choose that life if they could make up their own mind. The real truth is that when you, as cowboy devops, make a mistake that causes downtime or data loss, you bring huge losses to the company in downtime, loss of productivity, actual cash out, maybe even public perception if the fault is externally visible. The priorities are different, plain and simple, and rightly so. Enterprises have to protect themselves. Startups have to take risks. One way is not good and the other bad. They are just different. The idea that one needs to fight the valiant fight from within is absurd. Switch jobs to a smaller company! The author claims that it "feels like failure" which just means he is in the wrong job at the wrong company. That's all. It's pretty bad conclusion to hold up Bezos' mandate as some shining example. In reality it has caused lots of internal strife and Bezos is known to have pet projects and the rest of you losers can suck it. I do love, and will steal, the decagon of despair.