I can give you one example where something like that happened.
All of our services use credstash to store secrets. We use KMS in order to encrypt, decrypt the secrets and when the app loads we load all the secrets into memory.
There was a major change to cryptography that caused credstash to break and in turn break a large set of our services.
This PR [1] was submitted by one of the engineers to force the lower version to credstash and we opened the dependencies again to reload credstash on all services.
The process to track it down and fix it took about an hour and all services were building correctly again.
We make a very conscious choice to break those things in real time and deal with them rather than hiding them behind locked dependencies you simply never upgrade.
In London I'll often use Google Maps to search for the business that I'm looking for, then find the closest tube stop on the map and switch to Citymapper to navigate there.
How do you find companies that follow this or a variant over the traditional process. I've been interviewing at companies over the past couple of years and I've only participated at 1 take home task (startup) and know about 1 other company (on my list) that follows that.
I, like others stated above, tend to perform much better in my own space and time than under eyes on a whiteboard..
+1 -- This is where I learned to code actually. He has some really nice -long- courses for quite a few languages. When I first started I went through his VB.NET videos -- it's 200 videos, and it starts with something as simple as variables, but by the end you're doing real projects like calculators and simple video games.
Bucky! It has been many years since I saw that name. Made me smile, it is where all my real programming started. I would love to send him something out of gratification.
For the curious this was the content of the email. Pretty generic.
"Dear Let's Encrypt Subscriber,
We're writing to let you know that we are updating the Let's Encrypt Subscriber Agreement, effective June 30, 2016. You can find the updated agreement (v1.1) as well as the current agreement (v1.0.1) in the "Let's Encrypt Subscriber Agreement" section of the following page: