Public

I tend to think that folk who spout the "my code speaks for itself, I don't need to document it or comment it" nonsense are at best mistaken, and at worst toxic individuals who want to gatekeep the industry.

This is an interesting blog post that contains some thinking I can mostly vibe with.

I've been after something like this for ages. While I've generally always had my goto font for the terminal and editor, I've never really gone out of my way to decide which font really works for me.

This site does a great job of making it a "scientific" test, kinda.

A guide to building an interpreter for your own language.

One day.... one day.

While most of the article is written as a joke, I've seen some of these "dark side" approaches for code reviews done by actual people who don't seem to want to use code review to lift everyone.

Saving this so I can relive the trauma.

Instagram scaled from 0 to 14 million users in just over a year, from October 2010 to December 2011. They did this with only 3 engineers.

They did this by following 3 key principles and having a reliable tech stack.