Peter Erskine, Palle Danielsson & John Taylor As It Was.

Some obfusctaed Vim code.

Every macOS wallpaper from Mac OS X 10.0 Cheetah to macOS 10.15 Catalina combined.

Another reason for the bias toward over-engineering is asymmetric risk. If an over-engineered approach fails, you’ll face less criticism than if a simpler approach fails. As the old saying goes, nobody got fired for choosing IBM. — Scaling up and down

Overly Optimistic Prediction Results on Imbalanced Data: Flaws and Benefits of Applying Over-sampling.

High level C, by the author of Build your own Lisp.

Yet another enlightening post by Alexis King, that I will have a hard time to digest.

The flaw is in the premise: static types are not about “classifying the world” or pinning down the structure of every value in a system. The reality is that static type systems allow specifying exactly how much a component needs to know about the structure of its inputs, and conversely, how much it doesn’t.

Interesting use of recursion to split a time-series dataset for immediate consumption, which could certainly be applied when dealing with genetic data.

  Jack DeJohnette, Ravi Coltrane & Matt Garrison, In Movement.

Emotions cut both ways. For anyone who has released and maintained some moderately popular piece of software, you will have invariably made contact with other humans. The impact that another person can have on your emotional state can be staggering. A positive gesture or comment can really brighten your day. It’s that feeling: yes, sharing my code was so worth it just to help that one person. But as anyone who has been a FOSS maintainer can attest, positive comments are almost always dwarfed by negative comments. — My FOSS Story