> I mean work which somehow yields personal growth and future professional success I average 4 hrs of productive coding per day according to WakaTime[1]. When

> I mean work which somehow yields personal growth and future professional success I average 4 hrs of productive coding per day according to WakaTime[1]. When working on well-defined projects/features and not having meetings it goes up to 8 hrs coding per day, but that environment is difficult to create. Also there's the debate whether being productive means spending less time coding, or spending time towards the right problem (revenue, impact, team initiatives, etc). I also find the language and framework I'm using makes a huge difference in how much I accomplish given the same amount of time. When you're not sure if cranking out code is actually productive it's best to start measuring work in output velocity. For myself, I just assume when I'm coding in 2 of my projects I must be coding towards some goal, so I assume my time spent coding in those 2 projects is always productive. That's why I set a wakatime goal to code at least 4 hours per day in those 2 projects. 1: https://wakatime.com https://wakatime.com (Personal profile: https://wakatime.com/@alan https://wakatime.com/@alan)