When I decided to build a bulk fermentation tracking app the purpose was twofold:

1. Make timing of stretch and folds, and bulk fermentation easier to track.
2. Learn more about AI and how it can help with coding.

2026 will be my 30th year as a professional software developer and the constant theme throughout my career has been the need to continuously learn new skills. In the early days it was C++ and Java, then Ruby and Rails. Nowadays, whether you like it or not, you have to learn how to use AI as a tool — and I was behind in my learning.

Sourdough has a way of humbling you. You can follow the same recipe twice and get completely different results. For a long time I assumed that was just the nature of it — until I started paying closer attention to a few specific things. Here’s what actually moved the needle for me.

1. Tracking the start time of bulk fermentation

It sounds obvious, but I wasn’t doing it consistently. I’d mix the dough, get distracted, and lose track of when bulk actually began. Once I started logging the exact start time, I had a real baseline to work from. Everything else depends on it.

Sourdough baking is part science, part intuition. Most baking apps treat it like a checklist — set a timer, follow the steps, done. But anyone who has baked sourdough knows it doesn’t work that way.

Bulk fermentation time depends on your starter’s activity, your dough temperature, your kitchen’s ambient temperature, and a dozen other factors. A 4-hour bulk at 78°F is a completely different beast from a 4-hour bulk at 68°F.