Splitting engineering teams into defense and offense

This makes me want to delete the post.

Or the idea of an "interrupt handler". OP may find other SRE concepts insightful, like error budgets.

I resonated with your post Daksh. Keep up the good work

Don't do that! This was a great post with a lot to learn from.

The fact you came to a very similar solution from first principles is very interesting (assuming you didn't know about this before!)

Please don't.

I personally found the idea inspiring and the article itself is explaining it succinctly. Even if it's not completely revolutionary, it's small, self containing concept that's actionable.

Lowley surprised why there are so many harsh voices in this thread, but the article definitely has merrit, even if it won't be usefull/possible to implement for everyone

"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."

https://news.ycombinator.com/newsguidelines.html

Error budget or recovery cost tracking goes a long way towards defeating the We never have time or money to do it right, but we’ll find time and money to fix it later mindset.

I’m generally a strong believer in “if it’s not measured it’s not managed” so this seems like it would be useful to explore. I suspect it’s tricky to assign a cost to a bug though.

It’s tricky to assign impact, lost sales, revenue, customer satisfaction. Cost is just development and testing time.