24th Aug, 2007

Toughest parts first

One thing I’ve learned from working on some larger projects is if you have a long list of things to do, pick the hardest thing first. It’s tempting to start on the easy stuff because you can get it done fast, which seems good at first. But this gives you a false sense of reality.

If you start with the easiest parts of an application, you’ll think you’re doing fine and there’s not much more to do. Then you get to those last few key, difficult parts of the app and you slow down. Pretty soon that deadline you thought you would hit seems a bit unrealistic.

It’s also most likely the toughest part of your shiny new app is its selling point! Whatever part of the app is easy has most likely already been done. So don’t do the easy stuff until the end. You’ll be worn out anyway and could use the break.

Responses

Nice suggestion, although sometimes when i do the hard stuff first it doesn’t work out as i get demoralised and loose the much needed focus due to the seemingly impossible nature of the task.

I tend to get things done better when i plan ahead and split everything up into realistic targets. I also like to see things working, so if i am working on a project i try not to break it.

On another note i tagged you with the Scattergories Meme. If you have the time, and fancy a little challenge, please join in. :)

Categories