What you're saying is true if 'wasting time' was actually a problem. How often, though, in the course of reading a random news post or checking Twitter for the 478th time that day, do you realize the reason your program segfaults, or figure out to solution to making your application more modular and flexible?
While not an ideal use of your time, developers rarely stop thinking about the problems they're working on.
Now excuse me, I think I have an idea I need to go try out! ;)
I agree, that's why I suggest to not use time tracking as a final metric. I argue though, that such stats would show some interesting and not very obvious tendencies.
While not an ideal use of your time, developers rarely stop thinking about the problems they're working on.
Now excuse me, I think I have an idea I need to go try out! ;)