Editorial Policy

Who writes it

The guides and the explanatory notes attached to each tool are written and maintained by Enrique M., who is also responsible for the code behind them. There is no content farm, no freelance rewriting and no generated filler.

What we write about

Every guide covers a problem the author had to solve. The test is simple: would this have been useful to read before solving it? If a guide does not answer a question you actually had, it does not get published.

How we check the technical claims

• Behaviour that a specification defines is verified against the specification, and the guide links to it.
• Behaviour that a particular implementation defines is verified against that implementation's documentation, and the guide says which implementation it is talking about.
• Every algorithm in a tool is covered by an automated test with known-good values, so a regression fails the build rather than reaching a user.
• Claims about behaviour that varies between environments — timezones, locales, daylight saving — are stated as varying, with the specific case explained.

Corrections

When a guide is wrong, we correct it. Corrections that change a recommendation are noted at the bottom of the guide with the date, and the review date on each page changes when the content is revisited.

If you find an error, tell us. A wrong tool output is a priority, and a wrong guide is close behind — both send somebody down a path that does not work.

What we do not publish

• Content produced by a language model and published without being checked against the behaviour it describes.
• Pages generated by substituting one value into a template, which is what scaled content abuse is.
• Advertorial, affiliate content, or anything written in exchange for a placement.
• Listicles of tools we have not used, with no first-hand testing behind them.

Independence

No advertiser, tool vendor or platform pays for anything on this site, and nothing here is written because somebody asked us to write it. The tools we recommend are the ones we use, and the ones we do not use are mentioned only when they are the standard answer to a question.

How the tools themselves are reviewed

A tool page is not an article about the tool, it is the tool with documentation. The prose around it exists to explain what the tool does, where its limits are and when you would reach for it, and it is reviewed on the same schedule as the guides.