Reviews

Reviews after months in production, not after the first demo

What a tool is like once the novelty wears off and the traffic arrives.

4 guides · latest Oct 23, 2026

A review written on day one tells you whether the install worked. That is the easy part. These posts cover what happened in week six, when an update renamed a config key or a token bill jumped four times in a week.

Each review states how long I ran it, on what traffic, what it cost, and the specific thing that made me keep it or drop it. If I stopped using a tool, the post says so at the top rather than burying it in the verdict.

Start here

AI Code Assistants: Cursor, Claude Code and Copilot in Production

Six months of AI coding assistants on a real .NET and Python codebase: where they genuinely help, where they generate noise, and what they cost.

3059 words · Oct 23, 2026

Reviews

Reviews questions

Do you keep using the tools you review?

Most of them, yes — that is why they are on the site. Anything I dropped is marked as retired in the post instead of being quietly deleted.

How are review units obtained?

Bought with my own money unless the post says otherwise. If a vendor ever provides credits or a plan, that line goes in the first paragraph, not the footer.

Why are there fewer reviews than tutorials?

A review needs a month of runtime before it means anything. Tutorials can be written in a day. The ratio reflects that, not a lack of interest.

Keep going

  • Tutorials Reviews stop at the verdict; the build steps live here.
  • Comparisons Two candidates, one table, if the choice is still open.