Matthew relates software development to building boats:
“There are things you as the owner can see and cannot see and you will likely pay me no matter what. However, I know every piece of wood, every corner, joint, mortise, tendon, and grain direction. I know what the wood was, how it needs to be re-formed and what it should become. I could very easily do just enough to pass your visual inspection, bill you and move on; but I learned a long time ago that what you cannot see is just as important as what you can.”
I have found that the investment in quality is always worth the effort. It may seem that the parts you cannot see don’t matter, but they do become tangible in 1000 different subtle ways. The item will feel sturdier, will last longer, will be more flexible to changing environments, etc. It’s a good strategy for boats, and it’s a good strategy for building software too. I guess I’d put it this way: the person that buys the boat (or software) may not see the value, but all of the people who come in contact with it over its lifetime, will be able to tell you if it was well built or not. That’s quality.
Tags: quality, software development
monthly email
RSS 2.0