Stats

Ratings
Brews
Show

Custom range

Filters

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

All time · Mountain Time

4 brews4 brews .

Rating by wait

Rating by wait
  • Adjusted rating of this period's brews, by the days a bag had rested at its first brew.
  • Freezer days are not counted.
  • It compares bags, not brews of one bag.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).

No rated brews with a roast date in this period.

Rest window

Rest window
  • The share of this period's brews made before, inside and after the roaster's rest window.
  • Each with its adjusted rating.
  • Brews of bags with no window are left out.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).
  • Before 6% —
  • Inside 88% —
  • After 6% —

2 brews without a rest window

Brews until dialed in, by water

Brews until dialed in, by water
  • Each bag's settle brew: within its first 6 rated brews, the first within 0.5 of their best half's average.
  • Per water: the middle bag's, in whole brews.
  • Bags with 6+ rated brews that started this period.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).

Median settle brew per water · Water filter not applied · Always all brews

Variables vs rating

Variables vs rating
  • vs bag: each brew's rating minus its bag's average this period, averaged over the row's brews.
  • Only bags brewed 2+ ways (2+ brews each) count.
  • Bands · Exact: group a setting into bands, or list each value (rounded).
  • Break down by: the same delta per roast level, process, origin or roaster (rows with 3+ bags).
  • Blank: no match.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).

Grind drift

Grind drift
  • Mean change in grind setting vs each bag's first brew this period, on this grinder.
  • One row per brew number in the bag.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).
#1 0.00
#2 0.00

Negative = finer. A4Z (Femobook)· Always all brews

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: