Why I Decided to Start Writing Tech Blogs
“The best way to learn is to teach.”
Image credits: Photo by Nick Morrison on Unsplash
“The best way to learn is to teach.”
I used to think that was just a feel-good quote. Now, I see it as a compass.
If you’re an engineer, enthusiast, or someone trying to break into tech, you’ve probably felt this: There’s no shortage of resources-but there’s a shortage of context.
That gap between knowing and doing is where I’ve spent most of my career. And that’s exactly the space I want to write about.
From Debugging Code to Designing Systems (and Everything in Between)
I began my journey in tech without knowing the local language, straight out of college, working in Japan. Since then, I’ve done backend engineering, developing for Linux and Android, tinkered with custom AI solutions, custom libraries, and worked with specialized hardware and edge devices.
I’ve led development on various stages, contributed to product roadmaps, and even dived into infrastructure setup-wearing multiple hats in startups and fast-moving teams. But here’s the truth: Each new role and responsibility taught me how much I still didn’t know.
That humbling realization is what keeps me learning-and now, writing.
Why I’m Writing
To Share Without Sugarcoating
Most tech blogs filter out the rough edges. But the real learning often comes from the messy middle-things that didn’t go right, weird bugs that took days, or design choices that made sense… until they didn’t.To Clarify My Thinking Through a Third-Person Lens
Writing forces me to step outside myself and view my work, assumptions, and beliefs objectively. It often unlocks new patterns of thought I’d miss otherwise.To Share My Failures So You Don’t Have To Repeat Them
I’ve made architectural mistakes. I’ve overengineered solutions. I’ve chased shiny tech instead of solving the actual problem. If writing about these saves someone else a few hours-or a few months-it’s worth it.To Learn From You
This isn’t just about broadcasting ideas. I want to engage. Whether you’re an aspiring dev or a seasoned engineer with a different lens, I’d love to hear your takes.
What You Can Expect
This won’t be a niche-only blog. It will be as chaotic and random as my brain. In general, you’ll see posts on:
How I’m integrating AI into traditional systems
Lessons from building scalable backend systems with real-world constraints
How Android development taught me the importance of resource constraints
The curious bugs I find, and the elegant (or ugly) ways I solve them
Reflections on leadership as someone who prefers building over managing
You’ll also see me explore new tech stacks and areas I’m diving into, like Rust, LLM pipelines, or hardware-software interfacing, and documenting what works, what doesn’t, and what’s exciting.
Why This Matters (To You)
If you’re:
starting out and want to peek into the messy reality behind clean tutorials
transitioning from one domain (say, Android) to another (like AI)
trying to avoid common traps in system design, DevOps, or architecture
other interesting things :D
I hope this blog feels like a conversation with a learner/peer/mentor based on how far you are. I’ll share not just the how, but also the why and the what I’d do differently if I had to start again.
Because sometimes, the best way to grow fast is to stand on someone else’s failure.
Let’s Learn Together
Writing isn’t something I’ve done regularly before. This is a new habit I’m building.
I can’t promise a fixed schedule (yet), but I can assure authenticity, curiosity, and relevance.
This is an open space: for learning, sharing, and growing together.
Whether you’re here to learn something new, challenge a view, or just lurk and reflect-I’m glad you’re here.
What’s one mistake you wish someone had warned you about early in your tech journey?
Drop it in the comments. Maybe we can turn it into a post-or at least a good conversation.
Until next time
