I just finished an experiment.
For the entire month of January, I published a blog post every single day. Thirty days. Thirty posts. No breaks.
This wasn’t about proving anything. It was about learning—about my process, my limits, and what happens when you push a habit further than you’ve pushed it before.
The Setup
I’ve been blogging for years. At different points, I’ve tried different rhythms—once a month, once a week. Last year I published more posts than ever before, sometimes multiple in a day when the ideas were flowing.
But daily? That felt like a different challenge entirely.
The experiment wasn’t “can I write every day?” It was deeper than that:
- Do I have enough ideas?
- Can my process support this pace?
- What friction will I hit, and can I remove it?
- What will I learn about how I think and work?
Where the Posts Came From
I didn’t plan out the month. I didn’t create an editorial calendar or pre-write a bunch of drafts. It was organic, day by day.
Some posts came from my backlog—a long list of blog ideas I’ve been keeping for years. I’d randomly pull one up based on the title, see if it felt ready, and finish it.
Other posts came from talks I gave this month. I’d extract the core ideas and turn them into written form.
And some posts were completely fresh—captured during my commute. I’d voice out ideas while driving, and by the time I got to my computer, I’d turn the transcript into a blog post. These felt very fresh in the way I voiced them that day, but they weren’t necessarily brand new ideas. They were things I’d been thinking about for a while, making connections over time, and just happened to voice out and capture in that moment.
There were days when I didn’t know what I’d publish until early morning. Within about 30 minutes, I’d get the idea out, draft the post, refine it, and publish it.
That only happened because of the process I’ve built.
The Process That Made It Possible
Over the last year, I’d been using a project in ChatGPT with instructions on how to turn my ideas, thoughts, and journals into blog posts. It worked, but I’d been wanting to experiment with a different approach—using tools like Windsurf or Cursor instead.
So I took those instructions from ChatGPT and moved them into a plain markdown file that I could use in any AI tool. That’s been working well. I’ve been refining that prompt, and it’s getting me pretty close to a draft I’d want to publish.
I also ported over the instructions I use to categorize and tag blog posts according to the taxonomy I created a few months ago when I was cleaning up my 600+ blog posts. After I have a draft and refine it a little, I run two different instructions—one to categorize the post based on its content, and one to suggest tags from my taxonomy (anywhere from three to seven tags at most). I review those, then publish.
The process became smoother each week. I’d pay attention to the friction—where I slowed down, where I got stuck—and find ways to remove it.
What I Learned
It happened. It was not painful at all.
I was able to get one post out every single day, and the process allowed me to do it faster as the month went on.
So it is feasible. It is doable.
If I want to keep doing it, I now know I can.
But more than that, I learned something about the relationship between process and output. The posts didn’t feel rushed or forced. They felt like natural extensions of my thinking—because they were. The process didn’t create artificial pressure. It created a container for ideas that were already there.
I also learned that I didn’t need to plan everything out. The only two or three days when I prepared posts ahead of time was when I was at an off-site meeting for the weekend and wasn’t sure if I’d have time. So I scheduled them. It turned out I did have a little time to spare to go back, revise the posts, and get them out. But yeah, it was pretty much very organic as I went.
What Emerged
After the month ended, I did something I hadn’t planned: I used AI to analyze all thirty posts—to see what patterns emerged, what themes I’d been writing about.
The dominant thread throughout the month was AI as a thinking partner, not just a tool. I wrote about using AI to surface connections in my annual review, to structure stories for talks, to act as a lead architect in code reviews, to help understand problems instead of just generating code.
Multiple posts converged on the idea that clarity of intent is the real bottleneck—not tools, not speed, but our ability to articulate what we’re actually trying to solve.
I wrote about fundamentals that still matter even when AI writes code. About journaling and reflection as practices that compound over time. About personal growth through distance and perspective. About productivity by design, not by default.
I didn’t set out to write about any of these themes. They emerged because they’re what I’m thinking about. The daily rhythm just gave them space to surface.
What’s Next
I don’t currently know if I want to keep doing this daily. I just know it’s possible.
Now I’m using this reflection to decide: Does it keep improving my process toward building knowledge, insights, wisdom—and hopefully helping me help others achieve higher positive impact on whatever they’re working on?
If it does, I may keep doing it.
We’ll see.
Leave a Reply