How I review

Short version: I use the thing, I read the source, I tell you what I found. If I can't verify a claim, I say so. If something is great, I say that too.

News briefs

News posts are short, fact-checked against the source material, and labeled with the date of the source announcement. The goal is to tell you what happened in 60 seconds, with a link to read more if you want the full version.

Reviews and guides

Longer pieces get more time. I run the thing, I read the docs, I check the pricing, I look for what other people are saying. I disclose what I was given for free vs. what I bought myself. The grading scale (A/B/C/F) is plain: A is something I'd buy with my own money and tell a friend about; F is something I'd warn a friend away from.

Affiliate and disclosure

Some links are affiliate links. They never change a verdict. They're always marked with a disclosure line at the bottom of the post. I never accept payment for a review.

Errors and corrections

If I get something wrong, I want to know. I add a correction note at the top of the post and update the post date. I don't quietly edit the body — the original is preserved in the git history if you want to see exactly what changed.