Re:Twitter to start layoffs -internal email
by saagarjha on Thursday November 03, 2022 @10:44PM
(#33461361)
Services that aren't under active development break as the things above them change and they are put into environments they weren't in before. This is very normal and the reason you don't see problems happening because of this is either because you're moving slowly (which is a valid way to do things…but not typical) or your have an army of people keeping it all running smoothly.
[ Parent
| on HN ]
Re:Twitter to start layoffs -internal email
by origin_path on Friday November 04, 2022 @05:56AM
(#33464069)
Alternative take: I was at Google when they killed Reader. At the time they pulled the plug, Reader had already been destaffed for years and was kept going in one guy's 20% time. The infrastructure effectively ran itself - the underlying Google datacenter teams replaced machines when they died, everything else was automated.
My experience there was pretty consistent with that: if you leave things alone, they won't break. Virtually all breakage was caused by changing things. On a well automated system repairing the physical components, rolling OS updates from time to time and so on, is not a huge amount of work.