> I can't wait to see the "Write code first" article later this afternoon. </sarcasm> == Don't go looking for customers before you have working code. == Years

> I can't wait to see the "Write code first" article later this afternoon. </sarcasm> == Don't go looking for customers before you have working code. == Years of experience show sales and investment rounds go better if you can show an actual, working software. The solution doesn't have to be complete, nor perfect fit for this particular customer, but nonetheless, if you pitch, you better be able to back your words with something concrete. Don't even attempt to set pricing or commiting to delivery deadlines unless you have at least sizeable chunk of code working. At the very least have third-party libraries ready and pick a platform (hardware, OS and UI toolkit) that provides most of what you need. Beware that quite often what seems an easy endeavour upfront, show to be quite complex, perhaps even unachievable, as you start coding. Thanks to the halting problem, it's not possible to find that out without actually implementing the important parts of your software. Last but not least, before you start selling, have had written and delivered at least a few similar pieces software. Having experience in problem domain is crucial for producing commercial-grade software. # # # Phew, easier than it seemed -- which goes to show how little value is in such generalizations. At least in general ;-)