I’ve wanted to start a personal blog for years.
Not just contribute to company Medium publications or write the occasional guest post - I wanted my own space where I could share whatever nerdy thing I’m currently obsessed with.
But here’s the thing: I never did it.
Why? Because I’m a perfectionist. Every time I’d think about writing a post, I’d go through this mental checklist: “Is this interesting enough? Has someone already written this better? Do I have time to make this really good?” And since I have about seventeen different hobbies competing for my attention (homelab, 3D printing, mechanical keyboards, you get the idea), blogging always lost the battle for my time.
So I stayed in this loop: Wanting to write, not having the time to write perfectly, therefore not writing at all. Classic perfectionist trap, right?
Why It Was So Hard
Let’s be honest about what goes into writing a quality technical blog post.
First, there’s the actual writing. You need to explain complex concepts clearly, provide code examples that actually work, and structure everything so it builds logically. That’s already time-consuming.
But then there’s everything else: the editing, the reviewing, the “wait, does this even make sense?” moments at 11 PM when you’re re-reading your draft for the fifth time. I’d send drafts to friends with different technical backgrounds - some Android devs, some backend engineers, some non-technical folks - just to make sure the content worked for everyone. Because what’s the point of writing if only three people in the world can understand what you’re saying?
And here’s the kicker: I don’t have unlimited time.
Between my day job, my various hobbies and side projects, and actually having a life outside of tech (you know, playing video games, seeing friends, that kind of thing), where exactly was I supposed to find 10-15 hours to craft the perfect blog post?
The problem? I have a lot of different interests. Too many, probably. Whatever catches my attention - whether it’s a new tech stack, a hardware project, or some random rabbit hole I’ve fallen down - I tend to dive deep. And all of these interests compete for the same limited resource: time.
This creates another problem: I’d start projects with enthusiasm, get halfway through, realize I don’t have time to finish properly, and jump to the next shiny thing. Sound familiar? It’s the curse of having multiple interests and finite hours in the day.
So I became incredibly selective with blogging. “If I’m going to invest this much time,” I’d tell myself, “it better be worth it.” Every post had to be something I was genuinely proud of, something that added real value to the community.
But the real blocker? I’d convince myself that what I wanted to write about wasn’t interesting enough. “Someone’s probably already covered this better than I could.”
Here’s a painful example: I had a presentation I’d prepared for an internal conference at work. I thought, “This would be great for Droidcon London!” But then the perfectionist brain kicked in: “I don’t have time to refine it perfectly, to adapt it from internal standards to a public conference format.” So I put it on hold.
Then I went to Droidcon London anyway… and watched two other talks on the exact same topic.
Yeah. That sucks. 😔
This is what perfectionism costs you: while you’re waiting for the perfect moment, the perfect polish, the perfect conditions - someone else just ships it.
The AI Shift - Everything Changed in 2024/2025
Then something fundamental changed in the content creation landscape: AI became genuinely useful.
I’m talking about 2024-2025, when AI tools evolved into actually helpful writing assistants. The kind that can help you think through ideas, structure your thoughts, and iterate on drafts without losing your voice in the process.
Suddenly, you could:
- Brainstorm ideas and get immediate feedback
- Draft sections and iterate quickly
- Get help structuring complex technical explanations
- Polish your writing without spending hours agonizing over every sentence
- Cut your writing time from 15 hours to maybe 5
This way, the barrier to entry for content creation dropped dramatically. Tasks that used to take me an entire weekend could now be done in an evening. The tools got good enough that they could actually help you write better, not just faster.
“Well! This sounds great, right? 🤔”
More people can share their knowledge! The collective wisdom of the developer community gets amplified! Everyone wins!
And honestly? On the surface, this is great. Lowering barriers to knowledge sharing is genuinely positive. The more developers who can share what they’ve learned, the better we all get.
But here’s where it gets interesting…
The Paradox - Why This Made Things Harder
Here’s what I didn’t expect: AI making it easier for me to write also made me question whether I should write at all.
Think about it from my perspective. For years, the main barrier was time - I couldn’t justify spending 15 hours on a blog post when I had a hundred other things competing for attention. Now AI removes that excuse. Great, right?
Except now I’m facing a different problem: if everyone can spin up a technically correct blog post in an afternoon, why would anyone read mine?
Before, the effort required naturally filtered things. You had to be passionate enough to invest the time, or experienced enough to write efficiently. Now? The internet is about to be flooded with content. Actually, it already is. 📈
So I started asking myself harder questions. Not “Can I write a blog post?” but “Do I have anything worth saying that isn’t just adding to the noise?”
This is the uncomfortable truth: AI made it easier for me to write consistently, but it also raised the bar for what makes content worth reading. Being technically correct isn’t enough anymore when anyone can produce that in an afternoon. I need to actually be interesting.
And honestly? That’s scarier than the time commitment ever was. 😰
My Solution: The Personal, Multi-Disciplinary Approach
So if AI has lowered the barrier but raised the stakes, what’s my answer?
Go personal. Go multi-disciplinary. Focus on what makes my perspective unique rather than trying to compete on “who can explain dependency injection the best.”
Here’s what I realized: I don’t need to be the world’s foremost expert on every topic I write about. I just need to share genuine experiences, real problems I’ve solved, and honest perspectives on things I’m actually doing.
The Android ecosystem has thousands of tutorial blogs explaining the same concepts. But my blog isn’t just about Android - it’s about all the technical things I’m exploring. Android development, homelab infrastructure, 3D printing projects, AI experiments, and whatever else catches my attention.
How many blogs capture that full spectrum of a developer’s actual interests? Most niche down to one topic. I’m doing the opposite - embracing the multidisciplinary chaos that reflects how I actually spend my time.
That’s my angle. Not “just another Android blog,” but a space that reflects how I actually work and learn. I’ll use AI to help me write consistently, but the perspective? That comes from real experience - things I’ve built, problems I’ve solved, failures I’ve learned from.
This is my space. My experiences, my voice, my weird combination of interests.
What You Can Expect
Here’s the kind of content you might see:
Android Development - Architecture patterns, migration strategies, real-world problems I’m solving. (Like making Gson migration less painful or navigating multi-module architecture)
Homelab Adventures - Self-hosting services, automation experiments, infrastructure projects. The wins and the “why did I think this was a good idea at 2 AM” moments.
AI Experiments - Practical applications, workflow optimizations, how I’m actually using these tools day-to-day.
Conference Insights - Takeaways from events like Droidcon. (Like my recent reflections from Droidcon London 2025)
I’m aiming for monthly posts, but life happens - I’ll publish when I have something worth sharing, not on an artificial schedule.
Some posts will be highly technical. Some will be more reflective. Some might just be “here’s a cool thing I built this weekend.”
Let’s Do This
So here we are. After years of “I should really start a blog,” I’m finally doing it.
Not because I suddenly have unlimited time or all the answers. But because waiting for perfect conditions means never starting at all, and I’d rather share genuine experiences than nothing.
If you’ve made it this far, thanks for reading. Stick around - this should be interesting.
You can follow along here on the blog, or catch new posts when I share them on LinkedIn or X.
