Editorial policy

This page explains how posts are made, so you can judge how much to trust them.

Every post starts from something that was run

A post is published only when there is a record of what was actually done: the commands, the configuration, the output, the versions involved and the date. Code blocks and numbers in a post come from that record. They are not written from memory or generated to look plausible.

Each post ends with a short “How this post was made” note that states the environment, the versions and the date of the run.

How AI is used

AI tools are used on this site, and each post says how:

• AI-assisted, human-reviewed. The author ran the work, an AI model helped draft the text, and the author checked it before publishing.
• Drafted by AI from automated tests. An automated job ran a defined test in a clean environment, captured the results, and an AI model wrote the post from those results. Automated checks confirm that every command and number in the post matches the captured output. These posts are not read by a person before publishing, and they say so.

No post claims that a person tested something when an automated job did.

What is not published

• Posts with no first-hand run behind them.
• Summaries of other people’s articles.
• Lists of tools that were not actually used.

Corrections

Software moves quickly and posts go out of date. When an error is reported or found:

1. The post is fixed.
2. The “Updated” date changes.
3. If the correction changes the conclusion, a note at the top of the post says what changed.

Report a problem through the contact page.

Advertising and independence

The site is funded by advertising and, occasionally, affiliate links. Advertisers do not see posts before publication and have no say in what is written. Posts containing affiliate links are labelled.