Why I'm putting my notes online

I'm early in my dev journey, and if you looked at my GitHub a week ago you'd have found exactly one public repository — the README. Not because I haven't built anything, but because everything I've actually done has been sitting in private repos and an ever-growing Obsidian vault that only I could see.

That felt backwards. So this site starts from the notes, not from a portfolio of finished, polished, resume-shaped projects I don't have yet.

What's actually in the vault

A messier, more honest list than "look at my skills": comparative implementations of the same algorithm across six languages, study notes on agentic AI patterns, a terminal workflow I've slowly assembled tool by tool, and a roadmap I wrote myself for going from "knows C" to "full-stack, AI-literate developer."

Some of it is polished. Some of it is a half-finished note I'll come back to in a month and barely recognize. I'm publishing both kinds, because the messy ones are usually more useful to whoever's a few weeks behind me than the clean ones are.

Why bother, this early

Two reasons. First, writing things down in a way another person could read forces a level of clarity that writing them down for yourself doesn't — you can't wave your hands at "you know what I mean" when someone else is actually reading it. Second, I'd rather the first few years of this be visible and a little rough than invisible and only shared once it's "ready." Ready is a moving target that mostly serves as an excuse.

If you're a fellow builder, a recruiter, or just someone who ended up here from a link — the Notes section is the realest thing on this site right now. The Projects page will catch up.