Nobody had to ask for the logs
keryx has no users but me, and it still got seven bug reports in two days, all filed by one of my own agent sessions. Checking one meant reading exactly what the reporter had typed, which you don't normally get to do.

keryx has no users but me, and it still got seven bug reports in two days, all filed by one of my own agent sessions. Checking one meant reading exactly what the reporter had typed, which you don't normally get to do.

The tool had comments on under ten per cent of its lines and ninety pages of documentation built into the binary, and I'd argue that was one decision made for two very different readers.

I read the question my support bot had fluffed, gave the correct answer off the top of my head, and was wrong. The docs had fooled the person who wrote them.

The issue tracker is full of answers, which is exactly why my support bot isn't allowed to quote it. An issue can point at the docs, but it never gets to be the answer.

A spec, a how-to and a README walk into a repo. Only one of them should still be there in six months.

A post hit Hacker News and the analytics showed pages far heavier than a static site should be. The cover images were the payload.
