The story behind this blog: why I decided to write and what topics I'll cover.
I've been building things on the web for years. Shipping products, debugging at 2 AM, rewriting the same authentication flow for the third time. But I rarely stopped to write about any of it.
That changes now.
There's a pattern I noticed: every time I explain something to someone else, whether a concept, a debugging approach, or an architectural decision, I understand it better myself. Writing is just that process, scaled up.
This blog isn't about chasing SEO or building an audience. It's a public notebook. A place where I document what I learn, what I build, and what breaks along the way.
I'll be writing about the things I work with daily:
No tutorials copied from docs. If I write about something, it's because I've actually used it in production.
I have a few posts in the pipeline already, one on structuring Next.js projects at scale and another on the real-world challenges of working with on-chain data. They'll come when they're ready.
If you want to reach out, the links are in the footer. I'm always happy to talk about code, architecture, or whatever you're building.
Let's go.