Nathan's Musings

Tearing apart bad documentation may be cathartic, but there’s good documentation out there too.

I first came across ThreadX somewhere around 2021, during its stint as Azure RTOS.

There’s a phenomenon that I’ve been observing, and I think it’s time to share my thoughts.

I’ve been working in the software industry for 20 years (counting as conservatively as I can) this year, and sometimes people come up with weird styles and enforce them on everyone who touches their codebase.

Recipe first, commentary later.

Recipe first, commentary later.

Recipe first, commentary later.

Recipe first, commentary later. 15 minutes of work and 2.5 hours of baking.

Recipe first, commentary later.

Jeff Atwood wrote about FizzBuzz in 2007.

The other day, a friend of mine brought this to my attention:

Due to some recent events, I’ve found myself in the position of needing to track medicine intake.

A co-worker of mine (the incomparable Yohei Manabe) was looking at some disassembled ARM code the other day, and discovered something weird.

A co-worker discovered an amazing thing the other day.

Sometimes people ask me questions about what it’s like living in a different country.

If you don’t already, you should use an RSS(/Atom) reader.

First, context.

I’ve got an electric toothbrush.

When I tried to search for the demand version of dumping, I found a lot of articles about regular dumping.

Yesterday, in make, I talked about what Make does.

There are many resources out there for how to use make and some of them are very good.

I’ve been writing C code professionally since about 2006, and while I look at a lot of languages (I have varying levels of familiarity with Python, Erlang, Ada, Haskell, Go, Rust, C++, OCaml, D, Javascript, Prolog, Lua, Lisp, Bash, Perl, Forth…you get the…

This post is aimed at people who come from languages with automatic garbage collection and want to get a sense for how to approach memory management in a lower level language.

This guide was last updated in July of 2026 with an 0.17.0-dev build.

This post is going to explain how pointers, arrays, and slices work in Zig, without depending on knowledge of other languages that use pointers.

Update: April 2024 - A lot has happened since I originally wrote this article.

This post is going to look at wrapping a C library in Zig.