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

10 brews10 brews .

Recipe report card

Recipe report card
  • Each recipe against your other brews of the same bags: positive = it rated higher.
  • Only bags brewed 2+ ways (2+ brews each) count.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).

1 rated brew has no flow data and is left out.

Technique

Technique
  • 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.
  • Brews without a flow reading still set their bag's average.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).

Pour count

Pour count
  • The number of pours, bloom included.
  • 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.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).
4 pours +0.4
5 pours −0.5

Bloom hold

Bloom hold
  • Seconds between the bloom pour and the next pour, to the nearest 10.
  • 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.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).
20s +0.3
30s −0.2

Pouring vs drawdown

Pouring vs drawdown
  • Mean pouring time and drawdown time of the brews in each contact band.
  • Pouring: first pour to the last.
  • Drawdown: the last pour to the end.
  • 2:00–2:29 1:40 + 0:40
  • 3:00–3:29 2:06 + 1:02

Pouring Drawdown, mean time per contact band

Drawdown

Drawdown
  • Time from the last pour to the end of the drawdown, in 30 second bands.
  • 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.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).
0:30–0:59 −0.5
1:00–1:29 +1.1

Swirls

Swirls
  • The number of swirls in the brew.
  • 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.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).
0 +1.0
1 −0.3
2 +0.3

Contact time

Contact time
  • Time from the first pour to the end of the drawdown, in 30 second bands.
  • 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.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).
2:00–2:29 +0.3
3:00–3:29 +1.1

Ratio

Ratio
  • Water to coffee, from the logged brew.
  • 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.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).
< 1:15.5 +0.3
1:15.5–16.5 +0.1
1:16.5–17.5 −0.1

Recipe × coffee

Recipe × coffee
  • Each recipe against your other brews of the same bags: positive = it rated higher.
  • Rows: the coffees, grouped.
  • Blank: no brews, or no match.
  • No match: no bag has 2+ brews of another recipe; the tip shows the cell's own brews.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).
Group by
Compare with
Nordic Light
Bean's Beans StandardBean's Beans Joocy

Below the bag's averageAbove

Rest age by recipe

Rest age by recipe
  • Days off roast at the brew.
  • Each recipe against your other brews of the same bags: positive = it rated higher.
  • Only 2 bags Low confidence: under 3 bags or 10 rated brews (4 for one coffee).
31–60
Bean's Beans StandardBean's Beans Joocy

Below the bag's averageAbove

Few brews are under 31 days old, so fresh-coffee rows are thin.

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: