Why I'm Finally Starting This Blog

I've wanted to write for a long time. Not because I wanted to become a blogger, build an audience, or establish myself as a thought leader — quite the opposite, actually.

Over the past twenty-plus years, I've had the privilege of working on some fascinating engineering problems. I've learned from incredible mentors, worked alongside talented developers, made more mistakes than I can count, and slowly developed opinions about software architecture, engineering culture, leadership, DevOps, AI, and what it means to build systems that last.

I've always wanted to share those experiences.

The problem was never having something to say

The problem was writing.

Whenever I sat down to write an article, it became an enormous investment of time. I'd rewrite paragraphs over and over, struggle to organize my thoughts, second-guess every sentence, and before long the article would be abandoned. Not because I wasn't proud of the ideas — because translating years of experience into words was simply exhausting.

So the ideas stayed where they started: in my head.

Then AI arrived

For the first time, the distance between a thought and a well-written draft became incredibly small.

It didn't suddenly make me more knowledgeable. It didn't invent my experiences. It didn't give me opinions I didn't already have. What it did was remove the friction that had kept those experiences locked inside my head for years.

Ironically, that created a new dilemma: should I even start writing now?

We're entering a world where anyone can generate an article in seconds. It has never been easier to produce content — and at the same time, it has never been harder to earn trust. If people know AI helped write this article, will they assume the ideas aren't mine?

I think that's a fair question.

A promise, from the very beginning

Everything you'll read on this blog starts with my own experiences:

• The projects I've built
• The architecture decisions I've debated
• The mistakes I've made
• The lessons I've learned
• The conversations I've had with engineers much smarter than me

AI is part of my writing process. It helps me organize ideas, improve clarity, challenge assumptions, and become a better communicator. But it doesn't create my experiences. Those are mine.

I don't see AI as replacing human expertise. I see it as amplifying it. To me, AI feels less like a ghostwriter and more like an editor that's available 24 hours a day — one that asks good questions, catches weak arguments, helps improve flow, and pushes me to explain ideas more clearly.

The thinking is still mine. The curiosity is still mine. The responsibility for every word is still mine.

So why now?

Because for the first time, I no longer have an excuse not to.

This is where I'll share what I've learned throughout my career. Some articles will dive deep into software architecture. Others will explore AI, DevOps, engineering leadership, developer productivity, or lessons learned from real projects. Some may simply be thoughts I find interesting enough to write down.

I won't always be right. But I'll always be honest.

If something here challenges your thinking, teaches you something new, or starts an interesting conversation, then this blog will have accomplished exactly what I hoped it would.

Thanks for reading. I'm looking forward to sharing the journey.

— Mike Kang