Lots of reading this weekend. This should keep you busy for a month of nights. At least.
Good series of articles on “what can we learn from Linux design”. The comments on some of the articles are better even than the articles.
- Ghosts of Unix Past: a historical search for design patterns
- Ghosts of Unix past, part 2: Conflated designs
- Ghosts of Unix past, part 3: Unfixable designs
- Ghosts of Unix past, part 4: High-maintenance designs
Older series from the same author:
- Linux kernel design patterns - part 1
- Linux kernel design patterns - part 2
- Linux kernel design patterns - part 3
No-Vacation Nation Revisited. It’s a little biased in terms of intent (there’s a thesis), but it collects a lot of data on vacation and leave across the richer part of the world.
The automation myth. The tag line is “Robots aren’t taking your jobs— and that’s the problem”.
http://dubeyko.com/development/FileSystems/NTFS/ntfsdoc.pdf. From the authors of the Linux NTFS filesystem, not Microsoft. Alas. Maybe the new Microsoft will see benefit to releasing documentation that’s accurate.
NTFS Forensics: A Programmers View of Raw Filesystem Data Extraction. NTFS on-disk layouts.
extra.fld. All the ZIP file extension fields known (to the Info-ZIP project, anyway).
Building and Installing Software Packages for Linux. Getting a bit old (this is from 1999), but still mostly relevant.
Linux From Scratch. Build a Linux distribution from scratch. Requires access to an existing Linux system. Good source of low-level details on Linux.
Visualizing Concurrency in Go. This is awesome.
Signals. Billed as “A lightweight “signals and slots” implementation using fast delegates.”. From 2004, and slightly updated in 2009.
ZL. Interesting. Basically C++ with Scheme-style hygienic macros.
Seesaw v2. Load balancer written in Go.
Introduction to the Autotools (autoconf, automake, and libtool). I’m not suggesting Autotools is good, it’s the opposite. It’s time to study everything so we can learn and grow.