Reading new software as an archive find

By Oliver Schmalzl · Written: 2026-10-11 · Archive discovery date: 2025-05-09

9 May 2025 · Archive date

A software announcement can still be interesting months later. It shows which idea was presented at a certain time and how a vendor explained its direction. It becomes a problem when the old text is treated like a current description of features.

An archive find therefore needs at least two dates: when the source appeared or was found, and when your own assessment was written.

A preview is one particular moment

An invented announcement could promise a new chart view. The video from that time shows a selected sequence. That does not mean the feature was generally available then, or that it works the same way today.

A good note keeps apart what was announced, what was demonstrated and what was documented. A later revision adds another question: which statements still apply, and which only refer to the old state?

For concrete steps, the documentation of the version you actually use is what counts. Old menu names and preliminary features should not slip unnoticed into today's instructions.

A look back can connect several finds

Instead of writing an almost identical text for each short announcement, you can describe a development: which tasks moved more into focus? Which forms of input were shown? Which questions remained open?

No performance rankings are needed for this. A factual look back can also show that product strategy and practical use are different things. The archive character stays visible, while the find gets a new context.

This way an older source is not artificially turned into news. It gets a place in an understandable development, without pretending to a personal experience that did not happen at the time.

Original finds

These links were the starting point for this post. The assessment in the text is my own; the linked posts are not my own tests.

About the date: This post was written on 11 October 2026. The archive date is the date of the earliest related find in the collection, not of a publication at that time. Technical assessments and sources added later refer to the time of writing.