fourth post in the training tracker series: turning the AI coach spec into a running endpoint, the bugs that only showed up once something real was talking to it, a security gap closed before a second user existed, and a chat UI to finally use the thing.
third post in the training tracker series: migrating the data model from single-user to multi-tenant before the second user exists, and writing the specs for an AI coach before writing a line of its code.
I asked one of these models how many days of the week have a ’d’ in them. It got it wrong — in different ways across different sessions. So I asked Claude to write about its own unreliability.
first post in a series documenting the build-out of a Canadian economic indicators dashboard.