https://silentoxygen.com/posts/Recent content in Posts on silentoxygenHugoenWed, 14 Jan 2026 00:00:00 +0000https://silentoxygen.com/posts/003-intro_to_c/Wed, 14 Jan 2026 00:00:00 +0000https://silentoxygen.com/posts/003-intro_to_c/<h2 id="an-introduction-to-c">An introduction to C</h2> <p>C is still everywhere for one reason: it maps cleanly to the machine. It gives you direct access to memory, predictable performance, and a runtime model you can actually understand.</p> <p>It also gives you enough rope to build reliable infrastructure—or to ship undefined behavior into production and spend the next six months chasing ghosts.</p> <p>Most “intro to C” material starts with Hello, world. That’s fine, but it teaches nothing about what makes C uniquely powerful and uniquely dangerous. If you’re learning C today, it’s usually because you’re close to systems: Linux, networking, embedded, performance tooling, or security work.</p>https://silentoxygen.com/posts/001-rust-introduction/Tue, 13 Jan 2026 00:00:00 +0000https://silentoxygen.com/posts/001-rust-introduction/<h1 id="rust-an-introduction">Rust: an introduction</h1> <p>Rust gets described in extremes. Either it’s “the future of systems programming” or “that language with the angry compiler.” Both are lazy takes.</p> <p>Rust is better understood as a language that takes correctness seriously enough to inconvenience you upfront. It trades short-term comfort for long-term reliability, and everything interesting about it follows from that choice.</p> <p>This document isn’t a tutorial. It’s a tour of the ideas that make Rust different — and why those ideas matter once systems get large, concurrent, and long-lived.</p>https://silentoxygen.com/posts/002-mlscpu-blog/Tue, 13 Jan 2026 00:00:00 +0000https://silentoxygen.com/posts/002-mlscpu-blog/<h1 id="building-mlscpu--systems-introspection">Building <code>mlscpu</code> — Systems Introspection</h1> <p>This post is about building <strong><code>mlscpu</code></strong>, a small Rust CLI that provides <code>lscpu</code>‑style CPU introspection on macOS. It assumes basic Rust familiarity, but focuses less on syntax and more on <strong>how Rust shapes design decisions</strong> when you are forced to confront the limits of your platform.</p> <hr> <h2 id="why-mlscpu-exists">Why <code>mlscpu</code> exists</h2> <p>On Linux, <code>lscpu</code> is deceptively good.</p> <p>It answers hard questions — topology, cache hierarchy, virtualization, feature flags — in a single, structured output. It doesn’t guess. It doesn’t invent values. If something isn’t known, it says so.</p>https://silentoxygen.com/posts/000-hello-world/Mon, 12 Jan 2026 00:00:00 +0000https://silentoxygen.com/posts/000-hello-world/<h2 id="why-this-blog-exists">Why this blog exists</h2> <p>This is a simple place to write about SRE, systems, reliability, and things I’m learning along the way.</p> <h2 id="what-i-plan-to-write-about">What I plan to write about</h2> <h3 id="site-reliability-engineering">Site Reliability Engineering</h3> <p>Notes on availability, incident response, and operating distributed systems.</p> <h3 id="systems-and-infrastructure">Systems and infrastructure</h3> <p>Low-level details, tooling, automation, and architecture tradeoffs.</p> <h3 id="learning-in-public">Learning in public</h3> <p>Writing to clarify thinking and keep track of progress.</p> <h2 id="whats-next">What’s next</h2> <p>This is just a starting point. More long-form posts will follow.</p>