What do I do now? How do I do this? How can I minimize my risk? Why isnt it working? These questions have passed through the mind of every beginning programmer. My first suggestion is, Do not wing it; do not guess. Corporate programmers who continually choose to guess, wing it, or take a hip shot for the design rather than using the tools and information available to them are a (deservedly) vanishing breed.
Even the most talented programmer cannot look up at the ceiling and spin through millions of lines of code to imagine what would happen under any possible condition. Yet many programmers try to do just that, rather than take a well-planned, proven, orderly and certain path toward a sound design for solving complex problems.
All of the techniques you need to avoid winging it have doubtless been invented and refined; theyve appeared in some IT magazine, book, or software product available to your company, or been invented by your colleagues in the IT department. Now these techniques are being used by the most successful programmers in your company. So you must, first, observe how your successful colleagues have solved the very same problem youve been presented with. Then you will form your design, determining not to ask for too much help from anyone .