Public
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.
Hey! You! Yes, you! Looking for a senior hacker role? Want to work for the second biggest creator of comics called DC¹? Fancy working in a team and environment that, in my experience, is the nicest group of folk I’ve worked with in the 35 years I’ve been banging on keyboards for money? Think you could cope working with me? (Okay, fine, forget that last part).
Perhaps know someone who might like that?
1: I think. Honestly, I’ve not actually fact-checked that.
Someone's love letter to how everything is a command in Emacs. I tried to sell this approach for Textual, especially when the idea of a command palette was first raised. Sadly it never came to pass.
I think it would still be an excellent idea.
It's a Forth. It's a Lisp. It's lambda calculus. It looks like fun and also something I'd never actually really use.