DEV Community

Discussion on: Where the wild code grows

Collapse
 
nestedsoftware profile image
Nested Software • Edited

I think this is a really good article, and it makes an important point about motivation.

It reminds me of a situation I was in on a past project. I was doing some maintenance on an application. Initially, we were given a fair amount of freedom to work on our choice of bugs in the issue tracker. I would usually start with a difficult, high priority, issue to work on.

Once it was done, I was often pretty tired, so then I'd look for a few easy quick hits. Sometimes they wouldn't be particularly high-priority issues, but they took very little time to fix. The feeling of being able to close several bugs in a short time renewed my energy level, and I felt ready to tackle something harder again.

Later on, they changed the policy, and we were told to only work on the top priority issues. Sometimes I couldn't find anything easy in this list, so I had to slog through one difficult issue after another. I strongly suspect that my overall productivity went down as a result.

I understand that when a client is paying, they should be able to direct what is being worked on. Still, I do believe that if you want to get the most out of your developers' efforts, it is wise to give them some leeway.