3 ms·

Deploying to 100% of production when the option exists to do a staged rollout[0] isn't "breaking things in more obscure ways," it's ignorance or laziness. [0]

Deploying to 100% of production when the option exists to do a staged rollout[0] isn't "breaking things in more obscure ways," it's ignorance or laziness. [0] As mentioned in the article.

gitgud 6y ago
> "it's ignorance or laziness" Well this kind of bugs me, that explanation can be applied to literally anyone who's ever broken anything by accident. With the benefit of hindsight you can always call them out as ignorant or lazy. The circumstances in the article were not explicitly lazy or ignorant in my opinion. It was an unusually large update (2 gigabytes), which due to being able to deploy all servers simultaneously, created an outage. Now, sure they could have done a staged roll-out, but why were they even allowed to deploy to all servers like that? How much due-diligence to they need to do in order to do their job? Reminds me of [1] that guy who accidentally deleted the entire production database on his first day. Was that "ignorance or laziness"? I would say it's a failure of the company's internal processes and systems. [1] https://www.reddit.com/r/cscareerquestions/comments/6ez8ag/accidentally_destroyed_production_database_on/ https://www.reddit.com/r/cscareerquestions/comments/6ez8ag/a...