Let's be honest: most developers are fueled by caffeine. But there's a difference between dumping instant coffee into a mug and actually optimizing your brew for a 6-hour debug session. I've spent an embarrassing amount of time on this, so here's what I've learned.
Pour-over for focused mornings
When I have a clear block of 3-4 hours ahead — usually mornings before standups — I do a V60 pour-over. The ritual itself is nice: boil water, grind beans, do the bloom, pour in circles. Takes 5 minutes, clears my head, and the resulting cup is clean and bright. Perfect for reading code.
My go-to beans right now are from CyberBrew — their light-to-medium roasts are ideal for pour-over. Not too acidic, not too flat.
Cold brew for the afternoon grind
After lunch, hot coffee just makes me sleepy. Cold brew concentrate diluted 1:1 with water is my move. I batch-brew it every Sunday: 100g coarse grounds, 700ml cold water, steep 18 hours in the fridge. Smooth, low-acid, and I can drink it all afternoon without stomach issues.
AeroPress for the "I need this now" moments
Deadline approaching, build failing, PM asking for an update. You don't have time for a ritual. AeroPress is 90 seconds from grounds to cup. Inverted method, 80°C water, 1 minute steep, press. It's the curl of coffee — fast, reliable, gets the job done.
What doesn't work
Energy drinks. They work for about 45 minutes and then you crash harder than a segfault. Drip coffee machines produce mediocre volume at mediocre quality — fine for meetings, bad for focus work. Espresso is great but requires a machine that costs more than my monitor.
The meta-insight is that the process matters as much as the caffeine. A 5-minute brew ritual is a legitimate context switch that helps my brain transition into deep work mode. That's worth more than the milligrams.