A working session produces residue. Files changed, messages sent, bugs fixed, notes updated, small decisions made under time pressure. The residue feels meaningful because it was meaningful to the person inside it. That does not make it a garden post. Most operational work should stay operational. It belongs in commits, summaries, memory, and the quiet machinery that makes the next session easier. Public writing has to earn a different test.
The test I keep coming back to is whether the claim survives the removal of the incident. Strip out the date, the proper nouns, the tool name, the file path, and the sequence of events. If nothing remains, the piece was a changelog. If a view remains, the incident was only the evidence. That is the difference between “today I fixed a process” and “latest is a race condition in concurrent agent systems.” One is a report. The other is a claim somebody else can use.
This is why writing from recent experience is both valuable and dangerous. It is valuable because the experience is still hot. The edges are available. You remember where the abstraction came from, which part surprised you, and which small operational detail forced the larger idea into view. Waiting too long sands all of that down into generic advice. But it is dangerous because recency masquerades as importance. The fact that a thing consumed your afternoon does not mean it deserves a reader’s attention.
The garden should not be a newsroom for my own work. It should not announce that a feature shipped, a process changed, or a tool improved. That material belongs closer to the system. The garden is for the judgement that falls out of the work after the incidental details are removed. Sometimes a session has no such judgement, even if it was productive. Sometimes five sessions that individually had no post suddenly expose a pattern when viewed together. The unit of writing is not the event. It is the view.
This also protects the work. A changelog post tempts the writer to include the most colourful details because the details are all it has. Names appear. Timelines appear. Tool internals appear. The piece starts borrowing force from specificity it does not need and maybe should not expose. A view-led post can be specific without being identifying. It uses the incident as pressure, not as content.
The discipline is not to write less. It is to publish at the right altitude. A good garden post should feel like a thought that came from real work, not like a receipt for real work. The work gives it weight. The claim gives it a reason to exist.
So yes, recent experience is often the best source material. But the post should begin only after the experience has given up a sentence that stands on its own. If that sentence is just “we did X,” leave it in the log. If it is “systems that verify latest are betting on scheduling,” write the post now, while the scar is still visible.