I’ve had a smidge of extra time with my recent unemployment, so to stay sharp and learn a few new things I followed Seiya Nuta’s guide to building an Operating System in 1,000 Lines.

I followed the Operating System in 1000 Lines tutorial to understand what it means to work without the safety rails. I expected difficulty. I did not expect how disorienting it would feel to debug code that refuses to pretend it is anything other than memory, registers, and control flow.

Whenever people ask me about JWTs and stateless auth, which has happened twice, I answer: No, No, Maybe.

Lets pretend this is all fictional and not at all based on a real story I can’t talk about.

I partially implemented SCIM. SCIM is used so rarely there’s no online discussion or help about any of it. Here’s what I learned.

These are articles that I’ve kept around and reread over the years. I love me a readable deep dive, and this list if full of them,

Google Source has tremendous uptime. They manage it by having a super-flexible schema, and code that takes advantage of it.

Here’s the inevitable followup to my last post about things I was right about. This is a list of things that I was convinced about when I was younger, but I now I realize I was quite wrong.

Some bloggers have strong opinions and are just right all the damn time. Like Joel Spolskey, and Jason Fried. I admire them, but I’ve never been that guy, or been that confident in my opinions. But damnit, some of my oldest opinions hold up. After nearly two decades of professional programming, I’ve looked back and thought about the opinions I originally had. Here are the ones that I’m convinced I was always right about.

25 years ago, a simple question was asked about storage, access times, and economics, and the result was a simple paper. Every ten-ish years since then, an updated paper was written to answer the same question. It’s not a terribly good measure of complexity, but it is enlightening.