Build a program from A->Z

Question

I have read a lot of books about Microsoft Dot Net and I have learned a lot of things

• Object Oriented programming
• Windows User Interface designing
• Using SQL Server and XML
• Debugging an application
• Using Serialization and application Domains
• Deploying a Windows application
• Security and licencing

I know how to do all that, no perfect and very deep, but good. But my problem is that I CAN'T build an application. It's not about the idea, I have ideas.

The problem is that each time I start, I don't know how to start, where to start, how to design the plan, to debug an application while writing it or after, when to implement security, when to deploy and test it, if my application is missing a step, if it's compatible with other dot net frameworks, if it'll works perfect on all platforms....

I feel that I have some missing in my learning that prevent me from building a whole application, that is secure and when managed.

Am I missing another book, courses, lessons?? Or it's my problem? Can all people design plans or it's just limited to other people? Finally: What Shall I do? Continue learning and build an application (to sell it later) Or Just work part time until I complete study and find a full time job??

Answer 1

Don't start by thinking big. Start by thinking small. When you think big, you risk intimidating yourself.

When I start out by thinking too big, I can never find the right starting place and I go in endless thought circles much like what you are describing. If I can start on a small, realistic, and manageable task then I start making small amounts of progress. After one piece is done, then I can start on the next one. Of course I'll later go back and tweak previous parts but that's ok. At least I got started and am on the right track and not stuck in "where do I start" perfectionist limbo.

How do you eat an elephant? One bite at a time.

[Edit] Here's another idea: try to write a simple but complete app every day for a week. This will necessitate doing hack-y things and using half-thought out spaghetti code. But it will also force you to focus on reaching a real conclusion and evaluate which features are needed and which are just feature-creep.

I would not recommend this for many people. If you do it too long you'll build atrocious habits. However, for your personal mental block, this exercise may help.

If you do decide to do something like this, please post back here and let us all know how it went.

Good luck!

ps: great question. I'm sure many people face this same situation but don't want to ask for fear of looking bad. I know I've doomed many of my own personal projects because of exactly the reasons you described