I'm Nathan Wallace. Software developer, armchair philosopher, badass MC.
Decisions should be driven by objective metrics and measures whenever possible.
The sooner a feature is delivered, the sooner we can measure its efficacy.
Once we have data, use it! Refine, restructure, or even change tack altogether.
Whether designing a webpage or a low-level ABI, we should keep usability in mind at all times.
Software is never perfect or complete, so it's crucial to be able to change our program in response to new data, new ideas, or new circumstances.
Pair programming prevents bugs. Collaborative design illuminates blindspots. Two heads are better than one.
Efficiency-focused like Vim, Sway, and the shell, are worth the effort to learn not for speed but for customizability.Read
With their upstream-first approach, Purism's Librem 5 should become the best alternative mobile operating system.Read
Reading code is like reading any language. With practice, even LISPs like Clojure can become second nature. Learn to read and write Clojure fluently.Read
See how to use deftype to implement clojure.lang.ISeq so we can use regular Clojure functions on our custom type.Read