This article describes almost exactly why I think gradual typing is actually a good thing. Type checkers shouldn't get in the way of your code compiling. Yes, the language has to be designed with this property from the beginning. Yes, you should always enforce complete checking in CI. But you should also be able to try half-baked ideas.
If you have never used QLab, I recommend downloading it and tinkering for a little while. It is probably the best-designed native macOS app that I’ve ever come across, finely tuned by a handful of developers for something like 15 years. It’s a great reminder of what apps _could_ feel like.
In general, you should be thinking about the delivery semantics of the systems calling your code. Many very useful callers offer "at least once" delivery guarantees, implying that your system should behave idempotently to their calls.
Sad to hear of his passing - Glaser was prolific. I used to work fairly regularly with a company (Masque Sound) that provided audio equipment for Broadway shows. Milton arranged a beautiful illustration for their 75th anniversary. I still have a shirt with that drawing on it - it's a cherished possession.
If Postwoman doesn't tickle your fancy, I'd take a look at https://github.com/pashky/restclient.el. (I believe there's a vim equivalent, too.) You can save requests in a simple .http file, and check them into your codebase. Makes collaboration very simple.
I ran into this in the pre-webpack era where it was somewhat common to just concatenate JS together in a gulp build step. We imported code from two NPM modules, and each one was wrapped in an IFEE, but the first one didn't terminate with a semicolon. Not fun to debug.
Wait, really? That’s shocking to me - I would have assumed the entire link was encrypted E2E. Are there technical limitations that make this infeasible?