How to properly research and prepare before diving into a program
posted 4 years ago
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
I often find myself relying on Programming forums such as this one for help on how to approach any given situation. Ex; just before posting this I planned on asking "How to make a flexible text-based grid where the length and width are based on user input". Simply asking such a question may help me now but wont for future problems. How do you prepare yourself to start writing a program? Do you just start and figure it out as you go? What kind of preparation do you take?, and more specific to my original question, if I'm looking for a different approach to a situation, whether it be for flexibility, efficiency, etc.. where should i start in order to find the answer I'm looking for?
posted 4 years ago
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
It doesn't often happen recently that I'm writing a completely new program like that. But when it happens, I start by writing a simplified version before adding more features.
So in your example "How to make a flexible text-based grid where the length and width are based on user input" I would start out with "Make a text-based grid" and then add the "user input" part. Even for a small program like that it can be difficult to deal with all of the requirements when you start writing code.
So in your example "How to make a flexible text-based grid where the length and width are based on user input" I would start out with "Make a text-based grid" and then add the "user input" part. Even for a small program like that it can be difficult to deal with all of the requirements when you start writing code.
posted 4 years ago
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
Use cases is a good place to start. Gathering a cross-section of scenarios that provide examples on how the system is to be used and its expected behavior.
Keep an eye out for nouns and verbs, they potentially turn into classes and methods.
Keep an eye out for relationships like "is-a" and "has-a" witch potentially turn into inheritance and aggregation or attributes.
Keep an eye out for nouns and verbs, they potentially turn into classes and methods.
Keep an eye out for relationships like "is-a" and "has-a" witch potentially turn into inheritance and aggregation or attributes.
posted 4 years ago
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
About the only thing I can add to the excellent advice you've been given is to
1. Turn your computer OFF.
2. Write down the problem in English (or your native Language), including any questions you have, or things you don't understand.
3. When coming up with a solution, concentrate on What Not How.
HIH
Winston
1. Turn your computer OFF.
2. Write down the problem in English (or your native Language), including any questions you have, or things you don't understand.
3. When coming up with a solution, concentrate on What Not How.
HIH
Winston
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
| When you have exhausted all possibilities, remember this: you haven't - Edison. Tiny ad: Paul Wheaton's 16th Kickstarter: Gardening playing cards for gardeners and homesteaders https://coderanch.com/t/889615/Paul-Wheaton-Kickstarter-Gardening-playing |











