Hacker News Reader

aprilthird2021

I don't think this takes into account the reality of huge megacorps with tons of development teams situated globally who are constantly changing the codebase.

Incidents happen as code changes. Even once you fix it, the changing nature of the code can introduce more issues

View on HN

I've never worked at a megacorp, but if megacorp employees believe that it is more acceptable for them to cause issues for customers than a 3-dev company, that really seems like a skill issue for the megacorp.

If it is unacceptable to cause that downtime, you write code that makes the downtime much less likely

Often it's from slippage between 2 teams systems where a contract never existed. Often even the relationship causing the incident is unclear.

I expect the scale here is not apples to apples. A three person team is often on a small product and downtime is often a catastrophe like truly broken for customers. Meanwhile a megacorp is often many many large products and downtime usually means a piece of one of them is degraded.

My random guess is that the "downtime" is fairly proportional to the scale difference with megas probably taking the edge.

Reply on news.ycombinator.com