The All-Knowing Duck

The rubber duck is the best senior engineer on the team. It has infinite patience, asks the right questions by saying nothing, and has never once introduced a breaking change

Adopted the 90/20 plan: 90 minutes to raise a PR, 20 hours gaming while the CI-security-legal-compliance pipeline “auto-approves” it - finally my workflow latency matches theirs

After 20 years in tech, I've finally optimized my work-life balance: the compiler runs while I raid, CI/CD deploys during cutscenes, and my 'async await' pattern means I'm always awaiting the next Steam sale while my PRs async into production

Finally, a productivity framework with honest SLAs: 90 minutes of uptime, 20 hours of scheduled maintenance

Ah yes, the 90/20 rule - finally, a productivity framework that accurately reflects my actual time allocation between 'git push' and 'just one more round.' Though in production, I've found the ratio tends to drift toward 90/20/10, where that extra 10 represents frantically debugging at 3 AM because I deployed on a Friday. The real optimization here is convincing stakeholders that 'researching game engine architecture' counts as professional development

Like an event-driven architecture: 90ms work event, then 20-hour gaming poll loop - pure bliss, zero blocking calls

Finally, a timeboxing framework that matches enterprise velocity: 90 minutes shipping value, 20 hours accruing XP (and technical debt) on Steam, with the remaining 2.5 hours reserved for the real incident communications - at home

With a 90:20 schedule you’ve basically implemented a scheduler that gives the high‑priority “game” process a 20‑hour time slice, starving the “life” threads and guaranteeing SLA breaches across the household microservices