←back to thread

Splitting engineering teams into defense and offense

(www.greptile.com)
210 points dakshgupta | 1 comments | 14 Oct 24 20:07 UTC | HN request time: 0s | source
Show context
joshhart[dead post] ◴[14 Oct 24 21:09 UTC] No.41842050[source]▶
[flagged]
candiddevmike ◴[14 Oct 24 21:33 UTC] No.41842268[source]▶
Or the idea of an "interrupt handler". OP may find other SRE concepts insightful, like error budgets.
replies(1): >>41845477 #
wombatpm ◴[15 Oct 24 06:19 UTC] No.41845477[source]▶
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.
replies(1): >>41845618 #
dakshgupta ◴[15 Oct 24 06:38 UTC] No.41845618[source]▶
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.
replies(1): >>41875840 #
1. wombatpm ◴[18 Oct 24 02:23 UTC] No.41875840[source]▶
It’s tricky to assign impact, lost sales, revenue, customer satisfaction. Cost is just development and testing time.