Saving links preserves information, but rarely preserves judgment. A few months later, what matters is often not what was read, but why a solution was chosen and under which conditions it remains valid.
Four kinds of information an article should keep#
Context#
Explain which system, scale, and constraints the problem came from. Without context, an experience is easily reused in the wrong setting.
Decision#
State the final choice and the alternatives that were rejected. Readers need to see the trade-off, not just the conclusion.
Evidence#
Evidence can be a load-test result, an error log, user feedback, or official documentation. It determines whether another person can review the conclusion.
Boundaries#
Say where the approach does not apply. Technical writing is often most credible when it is honest about its limits.
Moving from a newsletter to a blog#
Keep the original publication date, convert the body to Markdown, and add a consistent set of fields:
description: the homepage and search summary;categories: a small number of stable themes;tags: the concrete technologies and methods involved;lastmod: the date of a later revision.
In short#
A blog is not another bookmark folder. It is a personal technical knowledge base that can be searched, checked, and revised over time.