Cognitive Fatigue Assessment
Are you “coding on fumes”? This tool combines the Samn-Perelli Fatigue Scale with a Psychomotor Vigilance Task (PVT) to measure your real-time mental bandwidth.
🧠 The Science of “Mental Bandwidth”
Software engineering is not just typing; it is the constant holding of complex logic states in your working memory. When you are fatigued, this “RAM” clears, leading to syntax errors and logic bugs.
We assess your readiness using two aviation-grade metrics:
⚡ Optimizing Your “Biological Prime Time”
Your brain cannot maintain peak output for 8 hours straight. To improve your score, consider aligning your work with your biological rhythm:
- Respect the “Dip”: Most humans experience a natural cognitive trough between 2:00 PM and 4:00 PM (the post-lunch dip). Do not schedule complex architectural decisions during this window.
- The 90-Minute Rule: Known as “Ultradian Rhythms,” the brain focuses best in 90-minute cycles. Pushing beyond this without a break leads to diminishing returns and increased error rates.
- Strategic Glucose: The brain consumes 20% of your daily calories. Stable blood sugar (avoiding spikes) is critical for maintaining the focus required for debugging.
❓ Frequently Asked Questions
Why does reaction time matter for coding?
While typing speed isn’t coding, reaction time correlates directly with alertness. A slowed reaction indicates “System 2” thinking (deep logic) is compromised.
How often should I test?
We recommend testing before starting a complex sprint (e.g., 9:00 AM) and again during the mid-afternoon slump (3:00 PM) to gauge if you should switch to low-cognition tasks like documentation.