A good breakdown is as follows:
writing code/tests/documentation: 33%
procrastinating (includes HN): 29%
design: 13%
debugging: 8%
task/team management: 8%
testing: 4%
waiting for compile: 4%
On the worst days, I spend about 50% of time procrastinating. This is why I stopped - the more I tracked it, the worse it got. The more I try to stop procrastinating, the closer something is to a deadline, the more likely I tilt.There were some patterns. Early morning and post-siesta were creative moments. These were perfect for design/debug/task management. Late morning were tired-focused moments. These were perfect for menial tasks, i.e. code and documentation.
When you're creative, your brain jumps all over the place, which also makes it prime procrastination moments. Focus is a bug; the human brain was not built for it. Which might be why many people code best late at night.
do whatever you want, you aren't a robot that could understand 'oh wow, i spend a lot of time watching youtube! I should study instead'
nobody would follow/pay for this, people know when they are procrastinating and wasting time