Will be fixed later.

These are articles that I’ve kept around and reread over the years. I love me a readable deep dive, and this list if full of them,

When Fernando Corbató accepted the Turning Award for, among other things, inventing the computer password, he described my new favorite bug.

Should you use full variable names, or abbreviated? The answer: doesn’t matter.

Who uses UML? The answer may surprise you! Unless you’ve spent any time working as a programmer, then the answer will not surprise you. Not at all.

C.A.R. Hoare thinks program languages should primarily support design and documentation, with programming being a distant third.

It took me too long to realize that the paper I just read was directly relevant to me. It was about teams. I was on a team. Why didn’t I get that?

Google Source has tremendous uptime. They manage it by having a super-flexible schema, and code that takes advantage of it.

Use two choices. It’s easy to get hugely better performance by moving from one choice to two choices. It’s very hard to do better.

Forming. Storming. Norming. Performing. Every writer who writes about teams all reference this one (and only this one) article, and those four stages. It’s foundational, and it rhymes.