MossBySea

About

One author, one rule: nothing gets written up here that I haven't run myself.

Who I am

I'm Moss. I work in content and data at an internet company — writing SQL, arguing about metric definitions, and automating the repetitive parts of content production. That last one is why I've spent most of the past year inside AI coding and agent tools.

The documentation and marketing pages for these tools are excellent. Pointing one at a job with a deadline is a completely different experience. This site is about the second thing.

What gets written here

Yes:

No:

How I test

So that posts can be compared against each other, every test follows the same rules:

  1. Same task. In a head-to-head, every tool gets the identical task — same data, same prompt structure, no swapping the problem halfway through.
  2. Real work only. I don't build a demo for the post. Demos systematically flatter the tool, and readers can tell.
  3. Failures get written up. Where it stalled, what it misread, how many rounds it took me to get it right.
  4. Costs stated. Subscription price, token spend, and the hours it cost me. The hours usually matter more than the subscription.
  5. Everything is dated. These tools ship a new version every few weeks, so each post opens with a test date and version numbers. If I haven't retested in three months, the post says so.

Where the money comes from

This site carries affiliate links and I earn a commission on some purchases. It doesn't change the conclusions, and the affiliate disclosure spells out exactly why — including the cases where I'd refuse to recommend a product that pays me.

For the record: this site is unaffiliated with my employer, nothing here represents their views, and I don't cover products related to my day job.

Corrections

If you find something wrong — broken methodology, stale numbers, a conclusion that doesn't hold — please tell me. Corrections go into the original post with a dated note. Nothing gets quietly deleted.