A hard part of solving weird issues and then describing them, is that in retrospect you always should've solved it earlier. It was usually obvious with the knowledge you have now. There were numerable junctures you should've made a different choice in.
But GETTING to those junctures ~is the skill~.

Another limitation is that it requires both devices be on the same network, and I’m always on VPN…

It's like the inverse to the @sogrady.org Travel Weather Rule!

So sorry to hear this…love to you and your family…

Is your goddamned web browser not already an everything app? I can do my online banking, book a flight, browse porn, read a book, and watch TV all in Chrome. What the fuck does an "everything app" mean if not that

The worst outages of my career have *all* been after deploy freezes.

The longer the freeze, the worse the mess.

We can do better than this. People deserve better. ✨

This is fantastic! Now I'm really having FOMO. Fun fact: the license plate of my first car was 1642T (the year Galileo died and the year Newton was born according to the Julian calendar - my dad was a physics teacher). I named the car Isaac.

"People skills sustain a career more than technical skills" Alex Chan, Flickr Foundation #monkigras

In my opinion, part of this depends on at what level you set your talk. If you set your audience level for beginner, I’d say you still need to cover it. Otherwise, probably 10 to 15 seconds would do.

How did I not hear about you seeing Prince at DNA Lounge???

Ha, cheers. I'm only acutely aware because I'm missing out.