Ask HN: Do you find working on large distributed systems exhausting?
What do you find exhausting?<p>One anti-pattern I&#x27;ve found is that most orgs ask a single team to handle on-call around the clock for their service. This rarely scales well, from a human standpoint. If you&#x27;re getting paged at 2:00 in the morning on a regular basis you <i>will</i> start to resent it. There&#x27;s not much you can do about that so long as only one team is responsible for uptime 24&#x2F;7.<p>The solution is to hire operations teams globally, and then setup follow-the-sun operations whereby the people being paged are always naturally awake at that hour, and allows them to work normal eight hour shifts. But this requires companies to, <i>gasp</i>, have specialized developers and specialized operators <i>collaborate</i> before allowing new feature work into production, to ensure that the operations teams understand what the services are supposed to do and keep it all online. It requires (oh, the horror!) actually maintaining production standards, runbooks, and other documentation.<p>So naturally, many orgs would prefer to burn out their engineers instead.