Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: