BE PATIENT AND TRY TO STOMACH THROUGH THE PREAMBLE:
There are thousands of cliche' quotes spanning thousands of years to express virtually the same thing -- "how do I fix a problem?" You may be rolling your eyes or making some other involuntary gesture to show your disgust but don't underestimate the requirement or ability to sufficiently express a problem or its subsequent solution (if one exists).
Let's say, you're in pain so you call a doctor. "It HURTS!" you scream over the telephone. The doctor replies, "Where?" You answer, "Well, all over my right arm but especially between my elbow and my wrist!" The doctor will go through several rounds of question-and-answer with you until the doctor ascertains you have a "open radial fracture several inches above your wrist" (your bone is jutting out through your skin and your bleeding all over the kitchen floor). The more DESCRIPTIVE you can be about a problem, the more encompassing a solution can be....
The first few step are non-technical... They're more conceptual in nature. Any good developer (in my humble opinion is artistic as most solutions to problems require "out'-of-the-box" thinking). Creativity in forming solution typically yields the best results.
1. Describe your problem as completely as possible. Remember that not logging off your computer at work has nothing to do with your now exposed, fractured bone and the blood loss you're experiencing -- keep the problem contained.
2. Start with the obvious, 10,000-foot answer to the problem. Then decompose the answer into smaller steps to create a logical process of execution that brings you closer to conclusion. This is where you begin to create your design.
After you've created a design, you can then focus on the smaller steps. Each small step may require even yet smaller sub-steps to accomplish one of the previous steps already defined. What developers do at this point is called "pseudo-code". It's the logical flow of a sub-step which is part of the solution to solve a problem.
If you do this, then the tool becomes an "implementation" detail. That is to say, you've completed the conceptual part and now you're ready to actually DO IT. C++ is just a tool and for the most-part; depending on the application and environment, you can use other tools to accomplish the same outcome (e.g. Java, C#, Assembly). Each tool for the appropriate job -- while you may be able to drive nails into a piece of wood with the handle of a screwdriver, it'd be much easier to do with a hammer.
END OF PREAMBLE
Keep a clean, concise design and follow it. Keep your function-points preserved and cogent to your implementation. Use the proper development tools for your application. Prepare a comprehensive test plan. Document until it hurts...
2007-08-29 15:39:09
·
answer #1
·
answered by Found my brain but lost my mind 2
·
0⤊
0⤋
1. Get a computer science degree.
2. Load up on Jolt cola.
3. Design, code, test, debug, repeat.
2007-08-29 21:36:41
·
answer #2
·
answered by link 7
·
1⤊
0⤋