I'm in a semi-management role, so 10-15 hours working directly on programming projects on a good week, zero on a bad one. Of that time, probably a quarter is s

I'm in a semi-management role, so 10-15 hours working directly on programming projects on a good week, zero on a bad one. Of that time, probably a quarter is spent running tests over and over again. For a project that's just applying something I've done a dozen times before, I'll probably spend half of the rest of the time just understanding the part of the codebase I'm applying it to. For something that's new or rusty, I'll spend 90% of the time in the beginning and 20% at the end researching or planning or just looking up APIs in the documentation.