In an era where most "Show HN" posts are LLM wrappers built in a weekend, here's someone who spent three years writing an operating system from scratch — and apparently enjoyed every minute of it. That alone makes this worth a click.

Hobby OS development is one of the most under-appreciated pursuits in computing. It forces you to confront the parts of the stack that frameworks and managed runtimes deliberately hide: memory management without a heap allocator handed to you, interrupt handlers you wrote yourself, a scheduler with no Linux to fall back on, drivers talking directly to hardware registers. The OSDev wiki is famously dense, the toolchain is brittle, and "Hello, World" takes weeks instead of seconds. Most people who start such projects abandon them after the bootloader stage.

Three-year retrospectives from this corner of the hobbyist world tend to be unusually substantive. Based on the title and tone ("loving every minute"), the post likely covers things a technical audience genuinely wants to read about:

• The arc of progression — from a multiboot stub to a kernel that schedules processes, manages memory, and probably drives a framebuffer or PS/2 keyboard
• Architectural decisions revisited — monolithic vs. microkernel choices made in year one that the author now regrets or vindicates
• The debugging stories — triple faults at 3 AM, race conditions in the scheduler, the specific moment paging finally clicked
• Toolchain reality — cross-compiling GCC, QEMU vs. real hardware, the agony of debugging without printf
• What it taught them — usually a much deeper appreciation for what Linux/Windows actually do for you

This kind of long-haul personal project is increasingly rare to see written up honestly. The author isn't selling anything, isn't pivoting to a startup, isn't claiming their toy kernel will replace anything. They just built a thing, slowly, because it was interesting. That's the spirit HN was originally built around.

If you've ever stared at a bootloader tutorial and wondered whether sticking with it for years pays off — this is exactly the post you want to read. And if you're a working engineer who's drifted into 10 layers of abstraction above the metal, it's a useful reminder of what's actually under your node_modules folder.