Linux Dev Time – Episode 156
Summary
Hosts Joe, Armalith, Kevin, and Andy discuss how deep developers should understand systems, balancing work efficiency with personal curiosity. They explore leaky abstractions in tools like UFW, Git, and Rust, noting when digging into source code or assembly is necessary. The conversation covers interview techniques, the loss of empathy for beginners, and the value of testing to validate high-level abstractions.
Topics discussed
Intro and support for Late Night Linux
How deep should your system understanding be?
Work vs. fun: Depth of learning and deadlines
Rust, LLVM, and knowing assembly
Abstraction layers in Python and Java
UFW, iptables, and leaky abstractions
Haskell memory models and email protocols
Reading source code and the 'ping' interview question
Git complexity, empathy, and cron syntax
GUI package managers and creating abstractions
Listen ad-free on Castria