Spend a little time on software reliability now instead of a lot of time later
You're going to spend time fixing reliability—but it's your choice whether it's during an outage or ahead of time on your schedule and for less costs. Which will you choose?
"We all know when things go wrong, it cost us a million dollars and it was really bad. Let's have that never happen again.
But when we say, I need every engineering team to spend one hour, one day a week on reliability, does everyone lose their mind, or is that a reasonable request? Can we amortize out the cost of that?
And that's actually how I view it is we're amortizing the cost. We can spend one hour a week up front, or once a month, we could lose two days to dealing with it.
That's a net loss in time. So I think giving teams the ability to plan this work, to do this work, to invest in it, and then as we discussed, you have to reward teams for the right behavior."
—Kolton Andrus, Gremlin CTO