Back to Blog
3 min read

Fifty-Five Days of Daily Writing

Fifty-five days. Fifty-five posts.

I started this in January as an experiment. I keep doing it because it’s become something I didn’t expect.

What I Expected

A writing habit. Clearer thinking. Maybe some useful posts for my blog.

That’s all happened. But there’s something else underneath it.

What Actually Happened

My opinions got more calibrated. Writing forces you to commit to a position. Then people react. Then you learn whether you were right.

I’ve been wrong in public a few times. Not dramatically wrong, but noticeably wrong. That used to embarrass me. Now I treat it as information.

I stopped hoarding ideas. Before this, I’d have an interesting thought and file it away for a “proper” post someday. Most ideas died in that folder.

Now I write the idea the day I have it. Most of them are smaller than I thought. Some of them are bigger. I wouldn’t know which without writing them.

The topics I return to have surprised me. I thought I’d write mostly technical posts. I’ve written as much about parenting, presence, and consulting as I have about Azure.

That’s the writing showing me what I’m actually thinking about.

The Rhythm

Morning coffee. Thirty to forty minutes. Most posts start as a question I want to answer.

“Why does prompt caching matter and why do I keep forgetting to bring it up with clients?”

“What does my son’s LEGO session have to do with debugging?”

“When does an agent make more sense than a workflow?”

The writing is the thinking. The published post is the evidence that thinking happened.

What I’ve Let Go

Early on I worried about quality. “Is this good enough to publish?”

The question shifted to: “Did I think clearly about something today?” If yes, it gets published. Length, structure, polish—these serve clarity, not the other way around.

Some posts are 300 words. Some are 1500. The word count isn’t the point.

The Unexpected Benefit

I talk to people differently now. When someone asks what I think about something, I have a more precise answer. Not because I’m smarter—because I’ve been practicing precision in writing, and it transfers to speech.

Clients have noticed. A few have asked if I consult on communication, not just technical architecture.

That’s writing paying forward into work.

The Hard Days

There are days when nothing interesting happened and nothing interesting came to mind.

Those are the best posts, actually. Writing from an empty state forces honesty. No interesting framing to hide behind. Just: this is what I’m thinking, even when what I’m thinking is mostly uncertainty.

Fifty-Five More?

Yes. Not because I’ve committed to a number, but because stopping would feel like choosing less clarity over more.

That’s not a good trade.

If You’re Considering It

Start with ten days. Don’t aim for quality—aim for consistency.

Write what you actually think. Not what sounds impressive.

Publish it even when it’s imperfect.

The compounding happens quietly, then all at once.

Day fifty-five doesn’t look much different from day fifty-four. But it looks very different from day one.

Start on day one.

Michael John Peña

Michael John Peña

Senior Data Engineer based in Sydney. Writing about data, cloud, and technology.