Why I Started Blogging in 2026
It took me a while to get here.
I’ve been building things on the web for a few years now: small tools, automation scripts, side projects that live in private repos and mostly help just me. For a long time, that felt like enough. I’ve always been the kind of developer who prefers writing code over writing prose, staying heads-down in the editor, and moving on to the next problem as soon as the current one is solved.
But somewhere along the way I realized: the act of writing forces a different kind of thinking. Explaining something clearly requires understanding it clearly. And understanding things clearly is exactly what I want more of. There were too many times when I found myself re-solving the same obscure bug six months later because I never bothered to document the fix.
Documenting the Process
The modern web moves incredibly fast. Frameworks rise and fall, best practices evolve, and tools that felt bleeding-edge yesterday become standard today. By creating a public log of my work, I want to capture snapshots of my reasoning at a specific point in time.
Writing is also a way to force myself to slow down. In our industry, it’s far too easy to sprint from one project to the next without pausing to reflect on what you actually just built. By forcing myself to articulate my thoughts, I want to turn those chaotic, late-night debugging sessions into permanent, structured knowledge.
What I’ll write about
Mostly technical things: web development, tools I’m building, and problems I’ve solved (and failed to solve). I want to share practical, real-world examples rather than just textbook tutorials.
Sometimes I’ll share thoughts on game development or interactive web experiences, like experimenting with Three.js or custom animations. Occasionally, I’ll include personal reflections on the tech industry and continuous learning when they feel worth sharing.
Who this is for
Honestly? Future me, first. If someone else finds it useful, that’s a bonus. The internet has given me countless solutions through random blog posts written by developers sharing their niche issues. If my writing can save just one person an afternoon of frustrating debugging, then keeping this blog will be entirely worth it.
So this is post one. Let’s see where it goes.