Software that works.
In production.

Red Green Leash: Keeping a Fast Coding Assistant on Track

I have used Test-Driven Development, TDD, since the early 2000s. It makes me faster and safer.

While developing LogEze together with a coding assistant I have a set of rules I expect the assistant to follow. They keep it on a short leash. The rules are not theory. They are what remained after many sessions where the assistant didn't follow the TDD process good enough in my opinion. I have published a snapshot of them at github.com/tsundberg/red-green-leash, so this post can explain the rules and send you there for the files to copy and adapt.

The tagline says most of it: "No green without red. No step without a human."

Bringing the User Back from Mobile BankID on an iPhone

Logging in with Mobile BankID on a phone goes like this: you tap "Open BankID" in the browser, the BankID app opens, and you identify yourself. Then, by default, you are left in the BankID app, and you have to go back to the browser yourself. Not a nice experience. We wanted LogEze to bring the user back to the browser without that extra step.

Run Your Coding Assistant in the IDE Terminal

For a long time I ran my coding assistant in a separate terminal window. Claude Code or Mistral Vibe on one side of the screen, IntelliJ on the other. It worked, but I had to switch windows to see what the assistant had done, and then find the files it had touched. More often than I like to admit, I didn't bother. I read the summary in the terminal and moved on.