One of the first things I did after I bought my home in Florida was to start looking for a boat to buy.

I didn't have any experience in operating a boat on the open seas, but I figured I needed to get me a big boat - one with two staterooms, air conditioning, color tv, all the neat toys.

The boat dealers were eager to sell me the boat I wanted. All except one. The salesman (Paul) said he wouldn't sell me a big boat. He said what I really needed was a 'starter' boat. Something small and reliable I could use to gain experience operating a boat in the ocean.

He explained that most people new to boating don't have any idea what they really need, and often get in over their heads by buying more boat than they can handle. And that's why there were so many seemingly affordable large boats on the market. Those were the boats people bought before they discovered the truths of operating a boat in the ocean.

I took Paul's advice and bought a smaller boat. And after a few months, I learned enough about boating to know I didn't really want a large boat at all. In fact, having a large boat in the area where I live would have be a huge costly mistake.

By starting with a small, inexpensive boat, I allowed myself room to learn, to make a few mistakes, and to have fun, without an overburdening investment in resources.

This same strategy can be applied with getting started as a product developer. Instead of trying to take on a huge project as your first project, begin with a 'starter' project. Something simple, easy and fun. That way you allow yourself room to learn, and make a few mistake, without risking the farm.