Chip

The in-app assistant that customers now know as Chip, and that does the building in Chip Build, is my own project. I started it on my own initiative before it was on anyone's roadmap. It has since become the centrepiece of the product, and it is where most of my work goes today.

Describe it, and it gets built

You tell Chip what you need, say a weekly summary of escalations per team, posted to Slack. It asks a few questions, shows you a plan, and then builds it: the tables, the pipelines, the views, grouped in one place. It sees what you are looking at in the app, so "fix this" means the thing on your screen.

It checks its own work

Chip writes tests for what it builds and runs them before anything goes live, using test layers. It can simulate an incoming ticket or Slack message, see what its pipeline does with it, and keep fixing until the tests pass.

It gets better over time

What Chip learns about a customer goes into a long-term memory, so the next conversation starts where the last one ended. Chip is itself a pipeline, so I can ask it to look at its own past runs and improve itself. You can also just talk to it, with voice.

It is far from finished. Every week it can build a little more on its own, and every week shows me something it should have done better, which is what keeps it interesting.