O que 9 artigos em 15 meses me ensinaram sobre escrever com constância
Eu tenho um padrão de publicação estranho. Cinco artigos em quatro meses. Depois sete meses de silêncio total. Três artigos em cinco semanas. Depois quase três meses de silêncio de novo. Um artigo. E aqui estou eu, tentando entender o que esse padrão realmente significa antes de simplesmente prometer "vou postar toda semana" e repetir o ciclo. Entre abril e julho de 2025, escrevi sobre os…
Over a span of 15 months, publishing nine articles taught me valuable lessons about consistency in writing. My publication pattern was peculiar, with five articles in four months, followed by seven months of silence, then three articles in five weeks, only to be followed by almost three months of silence. This cycle repeated itself, with one article in between and a final piece in July 2025.
This period of writing was not due to a lack of topics, but rather the energy required to reflect on those topics in written form. Upon returning in March 2026, the tone had changed significantly. The article "Architecture of Software is, in Truth, Decision Management" moved away from tools or warning signs, focusing on how technical decisions have long-lasting consequences beyond the decision-maker.
Two weeks later, "Systems Scale Just Like Organizations" continued this line of thought: architecture is not just code, it's a structure of decisions. Three weeks after that, "You Don’t Scale Systems While You Remain the Single Point of Failure" presented the most uncomfortable point, acknowledging that sometimes I am the bottleneck.
These three articles came in a burst of five weeks, followed by another lengthy silence of nearly three months until the July article, "Rollback Isn't a Backup Plan. It's a Culture," written in English to reach a broader audience. This pattern is not a sign of laziness, but rather a pattern of peaks: I write when my thoughts have matured enough to turn into text, not on an artificial calendar schedule.
The issue is that these peaks are unpredictable, and unpredictability is the opposite of what works for building consistent technical presence. Therefore, the change I am testing now is not "write more," but rather reducing the size of the step: instead of waiting for a full article to mature, I note a paragraph, a loose idea, or an unanswered question, every week, not just when the peak arrives.
If I produce an article, it's great. If not, at least there is a trace that my thoughts did not stop during the silent months, they were just not ready for publication. If you also write in bursts or have tried a cadence that did not sustain, please comment here what worked (or did not) for you.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
