3 ms·
There’s a lot of rakes. Some don’t bother anyone. Some are well-managed by others and don’t need your attention. Others you may not have the skill to pick up. Y
by vlovich123 5y ago
There’s a lot of rakes. Some don’t bother anyone. Some are well-managed by others and don’t need your attention. Others you may not have the skill to pick up. Yet still exist others that shouldn’t be picked up now.
Knowing which ones you should pick up, how many, when to timebox it etc is a skill in and of itself. I’ve never felt unrewarded for that but:
a) I already work very quickly. I try to pick up rakes in my spare time (ie my main work is blocked for some reason)
b) I generally try to make sure no one else is tasked with picking up the rake
c) I identify the rakes that are relevant to my work (I’m generally not fixing rakes in the Linux Kernel)
There’s another problem and this one has to do with organizational pain. Most organizations are set up to not listen to your external opinion. So if you pick up rakes there the other manager will be relieved of solving the problem while your manager isn’t getting enough of your focus on your current job which isn’t helping anyone (the other manager needs to hire someone and won’t even if you’re telling them they should)
Both sides of the coin have merit.