Seems like a good idea to me. Means if anyone gains access to your device while its unlocked, its less easy to side-load nefarious things while the device is out of your control.
His perspective on SRE really resonates and he shares some really great strategies and book recommendations for adoption of SRE practices, cultures and technologies without pretending he has all the answers.
I did something like this but linked it to Slack and put the printer in our office.
If you responded to a message with a printer emoji she (Her name was Tilly) would print the message (could even print images/first frame of gifs) in black and white.
Haproxy is brilliant, we've used it for years as a simple mesh on all our services, but we're considering moving to envoy as we need opentracing support to help understand how requests flow between services.
There's an opentracing integration coming very soon! We were hoping to have it available with the 2.2 release but there were still a few things to finalize.
I've wanted to build a similar system for supporting preview of articles on a CMS. Problem is, users may share multiple URLs with a user so a single JWT token in a cookie doesn't suit that flow very well. Each new link followed needs to extend an existing value with additional proofs (and remove old ones?)
Its amazing how many parallels I can see in some software houses I've worked at.
Scope creep, unclear prioritisation, poor roadmap breakdown, hero cultures. Its not an unusual situation at all, but it is unusual to be in such a public facing position, and to be able to grow to such a size without a product for sale.
Its like a tech bubble running inside its very own organisation.
