Inspiration
Specialty-coffee recipes are usually shared as static instructions: a dose, a grind setting, a temperature, and a sequence of pours.
In practice, a recipe is never truly static. The result changes with the coffee, roast date, grinder, brewing device, water, technique, and personal taste. When someone adapts a Chemex recipe to a V60 or changes the grinder, that knowledge is usually lost in notes, screenshots, or social-media posts.
I built brew.it.again() around a different idea:
A coffee recipe should behave like versioned code.
Instead of replacing the original recipe, every experiment can become a new version with a clear history of what changed, who changed it, and how the cup turned out.
while not perfect:
brew.it.again();
Built With
- codex
- firebase
- gpt
- openai
- pwa
- react
- typescript
Log in or sign up for Devpost to join the conversation.