|
Where to start is always a problem. That's why producing professional, commercial applications is a non-trivial process. You should learn right now, if you're serious, that product definition, followed by perceptual and logic design, has to take place before you even choose a language, much less sit at your monitor and pound on the keyboard. Lay out for yourself what you want in plain English (or whatever language you think best in). Divide it into functional parts: user interface, data and data storage requirements, necessary features, desirable features, and useless bells and whistles. Think of how you need to implement those things, and how that implementation influences your choice of implemention the other parts. If you fail to design your project you will be running a race like the rabbit -- fast start, then asleep under a tree, tired from rewriting and debugging and cursing and chugging caffeine and scotch, and smoking anything that burns. The turtle who thought in advance will beat the crap out of you, get to market, and take all the money floating around.
|