Why Does This Blog Exist?
Another personal blog. Another place for technical content. But why?
Let me start by addressing some reasons that do not apply.
I Do Not Blog For Fame
And by "fame," I mean it in the most relative sense of the word—I have yet to see a technical blogger sell out an arena.
The idea of starting a blog and writing viral post after viral post sounds appealing. Maybe even making it a full-time job—sitting on a beach somewhere, typing away. But as nice as that fantasy is, that won’t be this blog.
Don’t get me wrong—I’ll be thrilled if someone reads what I’ve written (and even more so if they find it useful or entertaining). I may even "advertise" the blog by posting on Hacker News or Reddit.
But I don’t expect more than the occasional reader. And in a way, I don’t want anything more than that.
First and foremost, I write this blog for myself, and I don’t want to fall into the trap of writing about things that don’t interest me just to attract more eyes.
I Do Not Blog As A Personal Portfolio
Some people advocate for blogging as a way to build a personal portfolio. The idea is that sharing your knowledge can help establish you as an authority on a subject—or at the very least, show potential employers that you know what you’re talking about.
And that’s a great and perfectly valid reason to blog. But again, that won’t be this blog.
I don’t want to write about things just because they might benefit my career. I want to write about whatever I find interesting.
Most importantly, I don’t want to feel pressured to maintain a "professional" writing style. I need the freedom to throw in an occasional poop joke without worrying about it staining my portfolio.
I Blog To Clarify My Thoughts
At its core, writing is how I test and refine my own knowledge.
You’ve probably experienced something like this before:
You're learning something new. You don’t know much about the topic yet, but you put in the effort—reading through resources, maybe even listening to someone explain it. And everything makes perfect sense.
Until you try to apply what you’ve learned.
Suddenly, you realize you don’t understand the topic as well as you thought.
This is the difference between passively consuming knowledge and actively applying it.
When you read or listen to something, it’s easy to mistake familiarity for understanding. If you’ve encountered the same information enough times, it feels like you know it. But that feeling is deceptive.
When you think about a concept in your head, your mind glosses over the gaps in your understanding. But when you try to explain it on a blank page, those gaps become painfully obvious.
And that’s exactly why I’m doing this. I want to build things that I find cool, and then put them out into the world. I hope that by writing about my projects, I’ll be forced to fully understand every part of what I’m building—deepening my knowledge along the way.
I Blog To Finish What I Start
I suffer from three chronic conditions: grand ideas, over-planning, and not finishing anything.
My list of project ideas keeps growing, yet somehow, I rarely finish anything.
When I start a project, I spend days planning how I should go about it. Then I dive into research, learning everything I think I need to know before I begin. And before I realize it, two months have passed—without a single tangible result.
I spend a lot of time planning and researching.
I spend barely any time actually doing.
This blog might be the antidote to all that busywork.
Instead of chasing world-changing projects, my new goal is to create short, interesting posts here.
By limiting the scope and timeline of my projects, I hope it’ll be easier to actually get the ball rolling.
And now, the key part of this post:
👉 I will finish my next project in one month (deadline: April 30).
👉 I will spend no more than one week planning and researching before I start building.
There! I’ve now publicly committed to actually finishing something.
I may be lazy.
But I will never be lazy publicly.