list of articles tagged @prog
“Guideline: Rust Style” (via): “Writing software is not just an act of writing for the compiler but writing for your reviewer and those who will debug and change the code in the future. It should be viewed as a form of technical writing and apply the same principles, including […] Inverted pyramid or Progressive Disclosure: lead with or highlight the most salient details, letting readers decide how much they want to dig into the low-level details […]” - this is relevant not only to Rust, I’d really like if more people followed this approach in any language and codebase.
♧ 2026-03-24“Flake Parts - Official NixOS Wiki” - a fairly simple explanation of the basics of flake-parts, that I can finally understand. (Even though still not super sure what’s the benefit of using them yet.)
♧ 2026-03-04
“Keynote: Rust in the Linux Kernel, Why? - Greg Kroah-Hartman” (via)
♧ 2025-12-13“Undefined behavior in C and C++” (via) — “In other ways, less intuitively, the difficulty arises because C is NOT simply high-level assembly, and does NOT always give you what the underlying machine gives you. (…)”
♧ 2025-08-13
A trick for decent speed of dev in Rust: to enable optimizations for dependencies (rebuilt relatively rarerly) in debug builds, with:
♧ 2025-03-08[profile.dev.package.“*”] opt-level = 3inCargo.toml(via).
“The difference between undefined behavior and ill-formed C++ programs” (via). See also especially muvlon’s rant in the discussion on lobste.rs.
♧ 2024-08-05“A Guide to Undefined Behavior in C and C++, Part 1” & Part 2 & Part 3 by John Regehr, and “Falsehoods programmers believe about undefined behavior” (via, via).
♧ 2024-06-07“Why you don’t need flake-utils” plus “Nix flake architecture in practice” (both via).
♧ 2024-05-16“Leaving Rust gamedev after 3 years” (via).
♧ 2024-04-27“Prefer Rust to C/C++ for new code” (via). Also, maybe then “Learn Rust the Dangerous Way”.
♧ 2024-04-25“The Rust compiler isn’t slow; we are” (via). TL;DR: try using
♧ 2024-04-25cargo tree, cargo-bloat, and “dependencies” stats on lib.rs to replace dependencies with simpler ones; e.g. maybe gumdrop is enough vs. clap for args parsing, and nom vs. lalrpop for parser generator.“Saved by NixOS Integration Tests, Surprisingly” (via)
♧ 2024-03-02
"The RISKS Digest. Forum on Risks to the Public in Computers and Related Systems" (1st issue from 1985, and still going strong).
♧ 2024-01-31
Verify if all tests compile successfully:
♧ 2016-03-24go test -exec echo ./…