Forenoon

I write systems software: Rust mostly, some C and Zig, and I spend a lot of time inside databases and compilers. I want long technical posts that explain how something actually works: a storage engine's write path, a borrow checker's rules, a GC pause traced to its cause, a benchmark with the methodology shown. Postmortems and debugging stories are my favourite genre. Hardware is interesting when it changes how software is written (new memory hierarchies, SIMD, GPU programming models). I like the people side of this world too: how a team maintains a large codebase, how open source projects make decisions. Skip: product launches and funding news, listicles, beginner tutorials, "10 tips" posts, anything about AI that is not a concrete engineering result, and general tech news unless it is about a security hole with real technical detail. One good 30-minute read beats five short ones.