You can also also view the full archives of micro-posts. Longer blog posts are available in the Articles section.
What’s even more surprising for Alex is the fact that his peers seem to be different. According to an extensive twitter and blog research he’s done in the past, the majority of developers find eternal happiness immediately after the perfect productivity setup is achieved. — Dev surprised his perfect vim/tmux/bash/xmonad setup doesn’t alleviate existential crisis
Lovely autocorrection by Git, although 0.1s is a bit too quick for me, especially when I don’t look at the screen (I often perform incremental commits using a combination of git add . && git amend, where amend is aliased to amend = commit --amend --reuse-message=HEAD).

Currently reading Common Lisp by Example, and I feel like it is quite a good introduction to LISP in just under 60 pages. #lisp
JavaScript for Data Science. Great work, but still I don’t like the omnibus word “Data Science”.
Rust Language Cheat Sheet. #rust
If you want a single piece of advice to reduce your bug count, it’s this: Re-read your code frequently. After writing a few lines of code (3 to 6 lines, a short block within a function), re-read them. That habit will save you more time than any other simple change you can make. — Don’t write bugs
Elements of C Style. #clang
Go is simple to read, Rust is complicated, C++ is familiar, Zig looks promising but is too young to judge. — A “better C” benchmark