If anything 20% is on the high side, for experts working in difficult (profitable) domains.
When we pointy-haired-bosses are doing our job right, producing new code is a much lower priority in the software engineer’s day, behind understanding and maintaining the important code that is critical to the objectives of the organization.
I’m not sure about the exact percentage but I don’t think it’s necessarily that far off. I spend a lot of time reviewing code, designing, documenting, reading documentation. Actually writing code is a cherry on top.
Doesn’t sound like a great software engineer to me
If anything 20% is on the high side, for experts working in difficult (profitable) domains.
When we pointy-haired-bosses are doing our job right, producing new code is a much lower priority in the software engineer’s day, behind understanding and maintaining the important code that is critical to the objectives of the organization.
I’m not sure about the exact percentage but I don’t think it’s necessarily that far off. I spend a lot of time reviewing code, designing, documenting, reading documentation. Actually writing code is a cherry on top.