The timing of this one is scary. I'm working on a mobile app that does a key exchange with a server before allowing a server-based registration or login. It's

The timing of this one is scary. I'm working on a mobile app that does a key exchange with a server before allowing a server-based registration or login. It's nowhere near as complex as your average distributed system. That said, I've run into a scary amount of the things mentioned in this article in my tiny little use case. Just trying to ensure a decent user experience (timing out a comms check after two seconds rather than waiting up to 60 seconds when the phone switches from networked to disconnected) in an async message exchange needs some crazy orchestration. Keeping the code clean means refactoring stuff I thought I had nailed two months ago. I've been programming for a long time, but this stuff humbles me. And happily, I love it.