Developing FAQ

Free, no account, no sign-up, no trial. The catch, such as it is: they were built for jobs I was already doing, so they solve those jobs well and adjacent ones not at all.

No. Every calculator on this site runs entirely in your browser — there is no server on the other end receiving your bed dimensions or your fabric prices, because the arithmetic happens on your own device.

Where a tool remembers something between visits, it is stored locally in your browser and never leaves it. The share links some tools produce put your numbers in the URL itself, which is what makes them shareable — worth a glance before posting one publicly.

That is what they were built for. They also work offline once the page has loaded, because there is nothing to fetch.

Tell me, and say what you expected and what you got. Every tool here states its assumptions on the page, so the disagreement is usually somewhere findable: a spacing convention, a usable-width figure, a rounding step.

Several of the numbers in these tools have been corrected because someone worked a real project and the result did not match.

Because they make a recipe worse to use, and the recipe is the point. The instructions are at the top of their own page rather than below a life story.

Some gear links are affiliate links and are marked where they appear. That is the whole of the commercial model.

A single Python generator that turns markdown and JSON into static HTML — no CMS, no framework, no build pipeline beyond one script. There is a small Node service behind it for the live kitchen feed and the newsletter automations.

The whole thing is hand-built, which is the reason it loads fast and the reason it occasionally has a bug in a place a framework would have handled.

A shared code framework — the reusable spine underneath the things I build. It is not a product you buy and not a company. Think of it the way I think of a sourdough starter, but for software: something kept alive across projects rather than made fresh each time.

Appliance data published from a real kitchen, on a schedule. It exists because a running system that reports on itself is a better demonstration of what I build than a description would be.

Occasionally. A small number of contract projects a year, chosen for whether the work fits how and when I can work — a defined scope, a realistic timeline, and a pace I set rather than one a deadline sets for me.

There is no services menu here and no availability calendar, because there is not enough capacity to warrant one. If you have something specific in mind, get in touch and I will tell you plainly whether it is a fit. Often it will not be, and that is not a negotiating position.

Ask, and say what you have in mind. Some of this is already openly licensed and some is not yet, and the honest answer differs by piece rather than being one blanket yes or no.

Because it is not a separate activity. Bread, a rag quilt and a piece of software are the same job to me: measure honestly, work slowly, keep the thing afterwards.

Every calculator on this site exists because I needed it for something I was already doing — yardage because I was cutting fabric, baker's percentage because I was scaling a loaf. Splitting that into a craft site and a consultancy would describe two people, and there is one.