Posts Tagged process

The finishing switch

Sometimes I get some ideas that are not that much tied to code, but are more about the process of developing website. I still think this is relevant to this blog so that is why I will post them here.


Ad agency or a business where deadlines are tight and project are from 1 month to 2 months long


When a project is long enough and the pressure is high, the developer (the last worker at the end of the chain) can’t stand looking at his work anymore, gets tired and unmotivated. This is not good for the project and for the individual as he is not happy.

Possible solutions

Here his my idea: if you could start two projects of about the same timeline at the same time, then at some point in time during the projects (about at 75%), you switch the developers from one project to the other. You would probably loose some time because the new developer would need to get accustomed to the new project, but in return you would inject some new energy in the project. The new developer would probably think more about the project than the previous one who would be demotivated and not caring as much anymore.

Why do this on 2 projects at the same time? Because finishing a project is probably not the best part.  If you do a switch, both developers would have started and finished a project so it would be fair for every one. Now, there might not always be 2 projects at the same time of about the same length, so one of my coworkers suggested that you could have this floating finisher developer, that for a little while only finishes projects and after that get puts back into the loop of starting projects. Another possibility would be to hire freelancers to help finish a project, in that case I wouldn’t let the freelancer alone, but it would still instill new energy.

For the 2 options where you are doing this in house, you pretty much need your developers to be very close, code in a similar manner and respect each other (coding knowing that someone else will use your code) so I don’t think this could happen everywhere, but I think the culture of your company should push towards a strong  developer fraternity, anyway.

What do you guys think? Is this possible? Would you see this happening in your company? Is this how you would fix this problem?