What 9 articles in 15 months taught me about writing with consistency

I have a strange publication pattern. Five articles in four months. Then seven months of total silence. Three articles in five weeks. Then almost three months of silence again. One article. And here I am, trying to understand what this pattern really means before simply promising "I'll post every week" and repeating the cycle.

Between April and July 2025, I wrote about the fundamentals: a platform engineering study plan, the signs that an infrastructure needs modernization, the strategic role of those who act beyond technical execution, the bridge between engineering and business. In the middle of this, I also wrote about work exhaustion — not because I planned a "different" article, but because that's what I had to say at that moment.

This article, by the way, still represents me the most in this first phase: it shows that consistency in producing technical content is not incompatible with admitting that sometimes I lack the energy to produce anything.

Then, silence. Seven months. It wasn't a lack of subject matter. It was the kind of period where the operation consumes all the energy that would be left to reflect on it — and reflecting in writing requires a different kind of energy than solving incidents.

When I returned, in March 2026, the tone had changed. "Software Architecture is, in Truth, Decision Management" is no longer about tools or warning signs — it's about how technical decisions carry consequences that survive far beyond those who made them. Two weeks later, "Systems Scale in the Same Way as the Organization" continues this line of thinking: architecture is not just code, it's a decision structure.

And three weeks after that, "You can't scale systems as long as you remain the central point of them" reaches the most uncomfortable point of the three — that sometimes the bottleneck is me.

Three dense articles in five weeks. And again, silence — this time almost three months, until "Rollback Isn't a Backup Plan. It's a Culture." in July, written in English, targeting a broader audience than the previous ones.

This is not a pattern of laziness. It's a pattern of peaks: I write when my thinking has matured enough to turn into text, not at an artificial pace on an editorial calendar. The problem is that peaks are unpredictable — and unpredictability, for those trying to build consistent technical presence, is the opposite of what works.

So the change I'm testing now is not "writing more". It's reducing the size of the step: instead of waiting for an entire article to mature, I'm recording a paragraph, a loose idea, a question still without an answer — every week, not just when the peak arrives. If it turns into an article, great. If it doesn't, at least there is a trail that shows my thinking didn't stop during the months of silence, it just wasn't ready for publication.

If you also write in peaks, or have already tried a rhythm that didn't sustain itself — comment here what worked (or didn't) for you.