How it got here
It grew out of Noella's Etch A Sketch, the toy my daughter and I built together. That toy is where I first put AI to work, trying to turn it into a scaled drawing program for the job. With a few different AI coding tools it became useful often enough that Noella's program went back to being hers and Hecker Sketch got a life of its own.
My family and I are installing radiant heat in a 10,000 square foot building right now from a Hecker Sketch layout and its step-by-step directions, and the install has gone great: measure a few points, lay the wire mesh as a grid, and it comes down to counting loops and running tubing out fast.
I build it the way I build everything now: I design it, I write code, and I put AI coding tools to work on the parts I hand them, then test what comes back. That is what makes a program this size possible for a hobbyist programmer with a day job: the geometry behind faces, solids, snapping and unfolding would have taken me years on my own, and the rest months, and instead it gets done in weeks while I spend my evenings deciding what it should do and whether it does it right. It is tested by scripts that drive the real program on Linux, Windows and macOS before every release, and there are about 1,700 geometry checks behind the tools.













