miniblog.

There are *so many* ways that reading a text file can fail. Maybe it doesn't exist, it's a broken symlink, it's actually a directory, it's not the encoding you expected, or perhaps you just don't have the correct permissions. Reporting good errors is surprisingly labour intensive.

Really cute approach to reporting type errors: when there's a type error, show an example of a runtime error that the type check has prevented! Data-Driven Techniques for Type Error Diagnosis https://escholarship.org/uc/item/59s4h4pv

I haven't found a nice way of reporting "N/N tasks done" in progress interfaces. Users don't like seeing "Baking cakes 10/10 (100%)", especially if the last cake is slow. It's weird to them to see 100% when you haven't finished, but mathematically it's logical.