I love the idea of taking well understood analog concepts and applying them to the digital remote workplace, but man, forced sync calls coming in on a whim without my control to ignore them sounds like my absolute worst nightmare.
This is a lot of upfront work, and signing up for continuous maintenance, computing costs, dealing with vendor-specific oddities, and a host of other concerns. Whatever is gained from this (being able to sign AWS phobic clients) must be substantial.
Absolutely. I mean, could you imagine F1 drivers having to negotiate the track with the 911s, Astons & Corvettes? They'd throw a damn hissy fit.
Not only does it make the race exciting from logistics/entertainment perspective, but at any given time there are multiple first place battles occurring. It's hugely entertaining.
For me, endurance racing (WEC) is quite a bit more fascinating and impressive than F1. Racing a car on the cutting edge of race technology for 2 hours is one thing, but 24 hours is a whole different ballgame.
It's not that anyone has forgotten, it's that a lot of people never learned how to in the first place. Every programmer community is riddled with these problems but the NPM world seems to be the worst. The ruby gem "american_date" annoys me to no end. It's just a highly-specific implementation of Time#strptime. Gah