6 ms·
> A hard-to-capture cost factor is keeping highly used services operational or replaced while doing work on it. Anyone who does any kindof "building" (whether
by granshaw 7y ago
> A hard-to-capture cost factor is keeping highly used services operational or replaced while doing work on it.
Anyone who does any kindof "building" (whether it be software engineers making schema changes, or a general contractor adding to an existing house vs building from scratch) knows this intimately, so really it shouldn't be any kind of surprise at all
- rafiki6 7y agoBut to the article's original point, the people conducting the research to prepare these reports are non-experts. So they wouldn't even know where to look for these figures.
- keerthiko 7y agoExactly. It's super evident to anyone who works on maintaining SaaS that is in production with at least a hundred users at any given time using it in real-time when you are trying to push features or fixes that even going down for a minute will result in serious service reputation damage. We engineer a lot of reusable scaffolding and reporting tools to modify our services in-situ with minimal/no disruption because it is a huge priority. Operating on public infrastructure is the closest real-world parallel. But to most people who work jobs where their choices don't directly influence customer service uptime (including a construction worker or a surveyor of construction for the same public works, as opposed to the project coordinator/planner/senior architect/engineer), this is an opaque cost.