Hello, World — Why I Built This Site
Five years on the surface. Time to go under — systems, databases, Python, and everything I've been trusting other people to understand. Learning in public.
I’ve been a frontend dev for five years, and lately one layer of the stack doesn’t feel like enough. I’m proud of what I’ve shipped — real products, hard problems, interfaces that hold up — but I keep noticing how much of the system I rely on without truly understanding. The deeper I go, the more I see how much there is left to learn, and that’s exactly what’s pulling me in.
I know how requests travel, how databases get queried, how a deploy gets out the door — enough to be useful, not enough to feel like I’ve mastered any of it. A computer is a much bigger machine than the slice I work on, and I want the rest of it: the runtime, the memory, the protocols, the operating system underneath, the way real systems are designed to not fall over. I don’t want to keep being the person who calls the abstraction and trusts it works. I want to be the one who could rebuild it if I had to.
My next steps are mastering Python, getting serious about databases, and going deeper into systems and backend design. Python isn’t the destination — it’s the lever. It bends to almost everything I’m curious about, so the time I put in there compounds across the rest. The real goal is the whole machine.
I’m writing here because I’ve noticed something uncomfortable: the stuff I think I understand falls apart the moment I try to explain it. So this blog is partly a journal, partly a forcing function. If I can’t write it clearly, I don’t really know it.
What I’ll write about
- My learning journey toward becoming a stronger software engineer
- Building with LLMs (RAG, prompt engineering, tool use)
- TypeScript and Python patterns I find useful
- Architecture decisions and the reasoning behind them
More posts coming soon. If something resonates — or you think I got something wrong — my contact info is on the home page.