Stats

Ratings and brews
Ratings
Brews
Show
Measure
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.

Habits

91% 254 of 278 days
Active days
133 days Jun 27 – Nov 6
Longest streak
1 PM
Peak hour
Wed 6.0 brews avg
Busiest weekday

By hour of day

Brews per day
Mountain Time · 9 back-filled brews left out

By day of week

Brews per weekday, averaged
 

Hour × weekday

12a1a2a3a4a5a6a7a8a9a10a11a12p1p2p3p4p5p6p7p8p9p10p11p Mon
Tue
Wed
Thu
Fri
Sat
Sun

Brew calendar

Feb 2026

MTWTFSS

Mar 2026

MTWTFSS

Apr 2026

MTWTFSS

May 2026

MTWTFSS

Jun 2026

MTWTFSS

Jul 2026

MTWTFSS

Aug 2026

MTWTFSS

Sep 2026

MTWTFSS

Oct 2026

MTWTFSS

Nov 2026

MTWTFSS
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: