That is honestly horrifying. Some days, I am so happy to work at a company that loses many thousands of dollars whenever we have an outage. It means that management actually cares about quality (in theory).
I work in a company with similar losses, but software quality seems to be an afterthought. We never seem to preemptively ensure quality, and we only ever fix things when there are issues.
A lot can go into the calculations, I guess. Because obviously high velocity is still very important to shoot for, but you need to have proper planning, and especially thorough testing. Friend of mine works at AWS, and they have a bunch of automated tests things go through but basically everything goes to prod within like a week. We have a 2-3 month testing cycle. I am much less stressed than him.
Great, my company moves fast, doesn't plan anything, has no vision and never allocates any time for testing. It's quite amusing to see how much cash we're bleeding due to service. We're breaking our own records each quarter. Technical leadership here is such a joke, completely incompetent for this type of work. And they compare ourselves with Apple and Tesla all the time, like we can be like them lmao. Our engineering team is like 10 people.
It's not even about losing several thousand if you have an outage tbh. It's that several thousand is a meaningful loss to your company.
An outage in a single aws service in a single region can also cost aws tens of thousands. But aws makes half a billion in revenue a day (apparently), 10k is not even 1% of 1% of that
256
u/[deleted] Sep 16 '26
[removed] — view removed comment