telekid

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.

With great power comes great irresponsibility.

I don't have any idea what you're talking about, but I nevertheless found this very entertaining.

Which ones? And ignored (and potentially irreconcilable) or deferred?

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.