Software that works.
In production.

A Revival for Test First, If We Don't Waste It

Using a coding assistant might turn out to be the best thing that has happened to Test-Driven Development (TDD) so far. This is the seventh post in my series about coding with an assistant.

For more than twenty years the objection to TDD was always some version of the same thing. No time. Too much typing. We will add the tests later. The assistant removes that objection. It types the test for you in seconds and it does not get bored doing it. On top of that, the path of least resistance with an assistant now runs straight through the test. I made that case in Fitness Functions for an AI Coding Assistant. To get useful work out of the assistant you have to tell it what done looks like, and a description of done that a machine can check is a test. TDD stops being the disciplined choice and becomes the efficient one.

Fitness Functions for an AI Coding Assistant

This is the sixth post in my series about working with an AI coding assistant. The earlier posts covered getting started, observations, rules, results, and communication. This one is about the gap between a rule the assistant might follow and a constraint it cannot get around.

Pipe Suggestions Straight to the Clipboard

My AI assistant suggests commit messages. For a while I copied each one out of the terminal by hand, selecting the text with the mouse and pasting it into my git client. It works, but selecting text in the terminal drags the line breaks along with it. The terminal wraps the text to fit its width, and those wraps come through as real line breaks in whatever you paste into. Then you have to clean them out.