Gaps are where the work is

Off-the-shelf software is very good at the things everybody needs. The awkward part is the bit between two products that were never designed to meet: the integration nobody enjoys, the product that almost fits, the script that grew into a load-bearing component with no owner and no tests.

The gap

That gap is usually where bespoke effort belongs. Not because the commercial answer is wrong, but because the gap is specific to one estate, and a general tool would have to be worse at everything else to be right about it.

Tooling in place

The discipline is in the shape of the tool. A command should be hierarchical and composable, so that the common path is the short one and the unusual path is still reachable. It should expose safe defaults and make the dangerous path explicit rather than magical — a tool that quietly guesses is a tool that eventually guesses wrong at three in the morning.

This is what Groan is for, and what the Glamorous Toolkit is becoming: not automation for its own sake, but infrastructure a team can understand and change. The measure of good tooling is not how much it can do. It is how little you have to know about it to use it safely.