Note:  The following thought should reside under several of my categories, but I’m aiming it at programming, so it is going there…

I had posted a link to a nice article about how the Pro musicians spend their limited and valuable time practicing.  One thing that positively JUMPED out is one small tidbit… Practice doesn’t make perfect.  Perfect practice makes perfect.  The concept is to instill perfect execution before increasing difficulty, then increasing difficulty, all the while continuing to perform perfectly.  Doctors and airplane pilots are excellent examples of this principle.  You ALWAYS want them to perform perfectly .  Sloppy practice only leads to sloppy execution.

I’ll let everyone in on a little secret… Software development is the same way.  Unfortunately, most books and/or classes do not teach perfect software development.  Few work environments allow for perfect software.  In fact, most books are about how to ‘save’ sloppy projects.  (There certainly are enough projects to make printing these books an EXCELLENT return on investment).  A better way to save a project is to put good practices in place *BEFORE* beginning.

Good software development practices can help accelerate a project.  They can even help kill a bad project before it leaves the gate.  Unfortunately, there is not an easy way to measure how much a practice helps/hurts the bottom line.  Unless one does BAD projects, there’s no way to measure when the GOOD ones happen.

More on this later…


2 thoughts on “Practice DOESN’T make perfect (perfect practice does)

  1. Interesting points, David – but I wonder: surely if there is a way to determine the cost of a bad project then there must be a way to measure the impact of a good project. Maybe it is the way we go about trying to determine what the ROI on any given project might be. It seems to me that we develop based on user and corporate specifications, but perhaps we need to define how any given project is expected to impact the bottom line FIRST, then go to Corporate and Users to help define the process of acheiving this expected impact. This would be a great time for an anology or alagorical example. But I don’t have one. So… you know… whatever.

  2. There are some excellent ways to measure healthy project. Unfortunately, nobody TALKS about successful projects. <grin> It’s like reading a murder mystery where the killer is caught in the first chapter. There’s no drama in reading book where the action is ‘here’s the plan, the plan is executed, all is done’.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s