Whittling Code
Over the past few months I’ve been increasingly thinking about two differing strategies for building software;
- Shifting left, doing a lot of upfront design and specs on how the resulting software should look and work (think plan mode in coding agents)
- Starting with a rough shape of the desired result, and whittling/carving it down to the desired state
I used to largely be for the first of the above two strategies, and I think there are still times where it makes sense to pull forward some of the design and implementation discussions - especially when working with a team on a larger project.
However, AI agents have made it pretty easy to go with the second path, where it's far easier to "one-shot" a rough approximation of the thing you wanted with an agent, and then you can begin to away at the first result to get closer and closer to the desired product.
I don’t have a piece of software or a book to sell you on how you go about whittling, and I think it varies from person to person and harness to harness, but you should optimize your own workflow and setup for whittling away at the software.