What's the best software analogy you've heard?

Question

Possible Duplicate:
What software analogies have helped you?

Hi

Quite frequently I have to explain things to Project Managers who sometimes want to know a little bit more about something, and sometimes I try and come up with some analogy that best explains it.

Now, I can't really kick this off with a good analogy because mine usually suck, but I would be interested in yours, or some you've heard that have been used to simplify explanations.

One analogy that does come up often is when explaining Interfaces (i.e. .Net) to which I usually explain in terms of a vehicle has a driver interface, and all vehicles must implement that interface so that anyone who can drive a vehicle will be able to utilise it.

Any more? Would like to hear some, both serious and humorous. Please close if a duplicate.

Answer 1

Open source is free, like puppies are free.

Answer 2

Sometimes people used to argue about whether software development was more like an art or more like engineering.

There have also been "construction" metaphors, which suggested that it's like creating a building (which was more approriate perhaps for the waterfall process).

Answer 3

Software is nothing more than an elaborate Rube Goldberg machine.

Answer 4

Writing software is like trying to solve the puzzle you're in the act of creating.

Answer 5

The best analogy, one that everyone gets, is to liken software development to gardening. It takes knowledge, experience, hard work, lots of maintenance.

Trees and plants (features) sometimes grow in ways that you don't quite expect, and you have to cope with that. Weeds keep sprouting (maintenance) and you need to keep on top of that. You might end up with a delightful garden or an overgrown horror.

You didn't ask, but the worst analogy has got to be brick laying. You cannot size up a programming job before hand in terms of bricks (function points), buy the bricks, hire the brick layers, and estimate to the minute how long the job will take. To think otherwise is naive or ignorant.

Answer 6

I read one recently about Managing Your Debt:

Yes, you can produce code faster at times, but you are taking out a loan against quality and future productivity...and if you don't take the time to pay off the debt (clean up the code), the interest costs will potentially crush you.

Answer 7

I forgot where I got this quote off, but i found it to be true and funny.

"Commenting your code is like cleaning your bathroom - you never want to do it, but it really does create a more pleasant experience for you and your guests." - Ryan Campbell