1 points | by muhammadbaibars 14 hours ago ago
1 comments
I built this to measure how much time I lose switching between coding projects.
It scans git repos, detects when you switch projects (different repo + >30min gap), and estimates the cost (20 min per switch to get back in flow).
Ran it on 15 days of my commits: 15 switches, ~5 hours lost. I'm pretty focused, but wanted to see if others struggle more with this.
Currently a Python CLI tool with --today, --week, --month, --days options.
Demo video: https://www.youtube.com/watch?v=x-2PE4HOWEQ
Curious to hear if this resonates or if I'm measuring the wrong thing.
I built this to measure how much time I lose switching between coding projects.
It scans git repos, detects when you switch projects (different repo + >30min gap), and estimates the cost (20 min per switch to get back in flow).
Ran it on 15 days of my commits: 15 switches, ~5 hours lost. I'm pretty focused, but wanted to see if others struggle more with this.
Currently a Python CLI tool with --today, --week, --month, --days options.
Demo video: https://www.youtube.com/watch?v=x-2PE4HOWEQ
Curious to hear if this resonates or if I'm measuring the wrong thing.