Stats

Ratings
Brews
Show
Unit
Group by
Show

Custom range

Filters

Caffeine, Default (caffeinated): ratings leave decaf out. Counts, cost and Caffeinated vs. decaf include it.

All time · Mountain Time

People
  • Per person: Totals and rates ÷ 2: an even split (Bean Conqueror doesn't record who brewed).
  • Household: Everyone's brews together.

Consumption

61g
Apr 15 13 brews · 210g
105 days by Feb 26

Grams brewed per day, averaged by month
* partial month

Bought vs brewed

Grams per day, averaged by month
* partial month

On hand over time

Grams left on hand at the end of each month
* partial month

Time to open

Time to open
  • Median days from roast to the first brew (freezer days not counted), for bags first brewed this period.
  • Open to finished: the first to the last brew, for bags finished this period.
  • The first brew is the open day.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).
Roast to open 55 days median · 233 bags
Open to finished 6 days median · 225 bags

By roaster

  • Shoebox74 days33 bags
  • H&S55.5 days24 bags
  • Big Sur61 days15 bags
  • Sey40 days12 bags
  • Bean's Beans55 days11 bags

By process

  • Washed56 days149 bags
  • Natural52 days27 bags
  • Extended Ferment Washed59.5 days14 bags
  • Honey56 days13 bags
  • Anaerobic Washed46 days11 bags
Built with help from Claude Code, an AI coding assistant How AI was used Contact

How this site was built

I built Bean Tracker with Claude Code, Anthropic's AI coding assistant. Here's who does what.

What I do

  • Set the direction: which features get built, and in what order
  • Drive the technical decisions, drawing on my experience as a Staff SRE, DevOps engineer, and software engineer: architecture, hosting, testing, and releases
  • Bring nearly all of the coffee knowledge, from recipes, gear, and pour structure to extraction, rest, and water
  • Shape every design: I review each spec and push back on layout, wording, and behavior until it's right
  • Test every change in a live preview, on desktop and on my phone
  • Set the engineering standards: tests at every screen size, shareable links for every view, signed commits, and staged releases
  • Own the data: every coffee, rating, and note, plus the judgment calls on it
  • Run the infrastructure the site lives on: hosting, domains, and backups
  • Act as project manager and technical lead, and decide what gets published, including this note

What Claude Code does

  • Writes nearly all of the code and automated tests, following my direction
  • Drafts the designs, specs, plans, and docs for me to review
  • Researches options and explains the tradeoffs so I can decide
  • Analyzes my brewing data to suggest values, which I confirm or change
  • Releases and deploys changes once I give the go-ahead
  • Often runs several AI agents at once: one builds while another reviews

Nothing ships without my sign-off. I review every change in a live preview, and automated tests plus a separate AI code review check the code itself.

Questions or concerns?

If you have a question, spot a mistake, or want something removed (for instance, a photo of your coffee's label), email me at [email protected].

v1.110.7 Last updated: Last deployed: