hatchnyc
Joined 10 years ago
Joined 10 years ago
Now if they had only bought a Mercedes as well, they could have chosen the self-breaking option to avoid the collision in the first place.
Many cars and especially planes & spaceships are have tons of systems like this.
I worked on a system that did things like in response to a primary datasource being offline would switch the queries it used to a different database to include substitute data and pass this back to be used instead until the primary store came back online. Three years after it was put in production this happened on one of the company's biggest and most important days of the year, and our SREs were sitting there calmly trying to solve the issue, ended up waiting until late at night to deploy a fix. It would have been reasonable for this service to just rely on the primary source, but we would have been offline for hours if this little trick hadn't been put in place.
For obvious reasons it is much more common to see this level of design in physical, life-critical systems like aerospace or automotive technology, but you do see it sometimes in software. Well designed services that under heavy load, various kinds of infrastructure failure, attack, or other kinds of scenarios well outside the bounds of normal expected operations intelligently compensate while signaling alerts with precise, useful information, and attempt whatever kind of recovery is possible.
This is hard to anticipate and often thankless to build in advance. It's always a stressful time when this behavior is visible, but it gives me a feeling of admiration for the perhaps long gone employees who built it.
Wildly off-topic but perhaps you’re turning off a TV without the streaming device itself shutting down?
I mean this is it, right? This is the big one. All these "tech" companies that are not actually selling software taking huge cuts off the top line, this can't be sustainable.
You can own the market for a while, but sooner or later someone is going to come along and disrupt you.
I am always amazed at how many repetitive tasks folks want to load up developers with. I think there’s a tendency among developers-turned-managers to see their job as crafting the perfect “program” of processes for their developers to follow, instead just automating these tasks. Like they say, the cobbler’s children have no shoes.