About this log

I'm Sachin. I run PilPili — a browser-game arcade of small games that start instantly, need no account and no download. I spent seventeen years in enterprise data analytics before this, and I am not a programmer.

The games are built by directing AI. I decide what gets made, I play everything, I judge what's good, and I answer the hard questions when something isn't — the code is written by AI under rules and automated checks that we have had to learn, break, and rewrite in public view. That working method is the subject of this log.

This is a build log, not a diary. I won't tell you what I did this week. Each post is a problem you might also hit — a quality gate that fails at random, a game that passes every check and still isn't fun, a name that clears every trademark search and collides with a malware family — with what it cost us and what the measurements said. If a post wouldn't be worth finding by a stranger with the same problem, it doesn't get written.

Two things you should know about how this log is made, because on this subject honesty is the whole point:

Everything here is drawn from the project's own records. Decisions, measurements and playtest notes are written down as the work happens; posts are edited out of that record, not composed from memory. Where a number appears, it was measured, and the date tells you when.

AI helps draft these posts, the same way it builds the games. I direct, review and sign every one. A log about building with AI that concealed its own use of AI would not be worth your trust.

What you will not find here: claims that AI makes game development easy, weekly output theatre, or advice untested by shipping. The games are the record; the record is checkable; when we were wrong, the post says so.

The games live at the arcade — this log is deliberately kept out of their way. If you want to reach me, the contact page works and is read by a person.