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

667 brews667 brews .

Matching: 156 bags, 740 brews

Sweet spots

Sweet spots
  • For each setting, the band your ratings favor for coffees like this.
  • First choice: the same bag brewed both ways.
  • +0.4: beat the same bag's other brews by 0.4.
  • Too few of those: bag averages across similar coffees, widening the group until there's enough.
  • Likely / Possible: the gap is 2×+ / 1.5–2× its margin of error (about 95% / 87% sure).
  • Early: ahead or looking tied, but too few bags to call.
Early
  • Ahead (or looking tied) so far, but too little data to call it.
  • More brews would settle it.
90°C or 91°C Usually: 90–92°C
Early
  • Ahead (or looking tied) so far, but too little data to call it.
  • More brews would settle it.
2 in the running Lotus - Mg/K 60/10 (880mL) looks higher · 1 bag Usually: Lotus - Mg/K 60/10 (900mL)
Early
  • Ahead (or looking tied) so far, but too little data to call it.
  • More brews would settle it.
3 in the running Usually: CT62
Early
  • Ahead (or looking tied) so far, but too little data to call it.
  • More brews would settle it.
Cafec T90 Usually: Cafec Abaca
Early
  • Ahead (or looking tied) so far, but too little data to call it.
  • More brews would settle it.
1:17.5+ or 1:16.5–17.5 1:15.5–16.5 looks higher · 10 bags Usually: 1:16.5–17.5
Early
  • Ahead (or looking tied) so far, but too little data to call it.
  • More brews would settle it.
20+g or < 16g Usually: 18–20g
Early
  • Ahead (or looking tied) so far, but too little data to call it.
  • More brews would settle it.
1.2.0 or 1.4.0 1.0.0 looks higher · 4 bags Usually: 1.4.0
Early
  • Ahead (or looking tied) so far, but too little data to call it.
  • More brews would settle it.
Maybe 60s+ Usually: 30–44s
Early
  • Ahead (or looking tied) so far, but too little data to call it.
  • More brews would settle it.
3 in the running Usually: 61–90 d

Top bags like this

Top bags like this
  • The bags matching these filters with the best ratings.
  • Score: each bag's average pulled toward the matching brews' average by 5 brews, so one great brew doesn't top.
  • SD: how much its ratings vary.
  • Small: consistent.
  • Big: hit or miss.
  • Under each: its roaster, then usual temp · water · dripper.
BagBrewsScore
SD · standard deviation
  • How much ratings vary from brew to brew.
  • Small: consistent.
  • Big: hit or miss.
  1. 1 Colombia Yoiner Mosquera Gesha Anaerobic Natural Shoebox · 85°C · Lotus - Ultralight Mg + K (900mL) · Graycano 6 0.71 8.2
  2. 2 La Terrazan Java Bean's Beans · 91°C · Lotus - Ultralight Mg + K (900mL) · CT62 4 1.03 8.1
  3. 3 Faysel Abdosh Triple Ferment Washed Big Sur · 91°C · Lotus - Mg/K 60/10 (900mL) · CT62 6 0.42 8.1
  4. 4 Ecuador Abel Salinas H&S · 92°C · Lotus - Mg/K 60/10 (900mL) · CT62 11 1.19 8.0
  5. 5 2026 William Ortiz; La Cabaña, Chiroso Sey · 92°C · Lotus - Ultralight Mg + K (900mL) · Graycano 12 0.72 8.0
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: