How we work

How we test#

We only publish a tutorial once its steps have been run from start to finish in a real environment. At the top of every tested article, you’ll see a box with the test date and the environment: tool version, operating system and, when it matters, the plan we used.

• Commands and code: we copy them straight from the article and run them. If something needs to be adapted for a particular system, we say so.
• Comparisons: we give each tool the same task and the same instructions. If we don’t have access to a tool, we don’t compare it based on hearsay.
• Prices and limits: these come from each provider’s official page, and the date we checked is listed in the article’s sources.
• Real-world cases: these come from our day-to-day work. We remove client data, passwords and server addresses, but we don’t dress up the results.

How we use AI to write#

We use AI in the process, just as we use it in the rest of our work. We don’t hide this: AI helps us research, organize notes, draft and check for errors. People choose the topics, test every step, check every fact against its source, decide what gets published and take responsibility for it.

At the end of each article, we note that it was written with the help of AI, and who reviewed it and when. We don’t publish realistic AI-generated images. We make the diagrams and screenshots in our articles ourselves.

Updates and corrections#

AI changes very fast. Every article shows the date it was last updated, and we review articles on pricing and comparisons whenever something important changes. If we find an error, we fix it. If the error changes the article’s conclusion, we say so in the text itself.

If you spot something that’s no longer true, let us know.

Independence#

Nobody pays us to say good things about a tool. The blog will be funded by Google AdSense ads, which are shown separately from the content and labeled “Advertisement.” If we ever use affiliate links, they’ll be flagged right on the link.