The Programmer's Fuel
There is a famous axiom in computer science (often attributed to Paul ErdΕs): *"A mathematician is a device for turning coffee into theorems."* The same holds true for developers.
Caffeine is a central nervous system stimulant. It blocks adenosine receptors in the brain, temporarily disabling your brain's ability to feel fatigued.
The Ballmer Peak Error
Many coders believe in the "Ballmer Peak"βa satirical graph suggesting productivity spikes at a very specific Blood Alcohol Content. The caffeine equivalent is very real. * 1 Cup: Focus increases. Bug squashing efficiency rises. * 2 Cups: Peak lateral thinking. You feel like a wizard. * 4+ Cups: The Jitters. You type faster but introduce infinitely more bugs because your working memory is fractured by anxiety.
How the Math Works
The tool models productivity using a parabolic bell curve formula. By taking your baseline tolerance and inputting the mg of caffeine consumed, the script maps your place on the Yerkes-Dodson arousal curve.
Peak cognitive performance hits the apex of the parabola. If your dosage pushes you past the top of the curve, the output applies an inverted secondary multiplier, drastically reducing your 'Lines of Code' (LOC) projection to simulate the negative impact of jitter-induced syntax errors and shattered focus.
Advanced Theory
In the realm of cognitive pharmacology, caffeine sits uniquely at the intersection of productivity enhancement and anxiety generation. It does not actually 'give' you energy; it merely initiates a high-stakes loan against your future neurological stability. By mathematically translating this bio-chemical reality into simulated output metrics (like Lines of Code written per hour), we vividly chart the hidden velocity penalty that occurs the exact moment your adrenal system hits its saturation threshold.