Searching for a better way to making programs with a plan or something.
I've heard from a friend that there is a way to make a map that can help you with making programs. He thinks that I shold start with learning how to make these maps. Can you tell me where can I find a tutorial about this and explain a bin about the topic?
Thanks.
You mean a flow chart?
Quzah.
Hope is the first step on the road to disappointment.
Yes man! Thanks! Thats the one. If I plan to create software do I need to start with these flow charts?
Last edited by Laser; 11-15-2003 at 02:17 PM.
Its not a bad idea to use a flow chart.
Ok. A good program dosnt have to have one at all costs. Right?
Is it better to do a chart before writeing the program?
If someone knows a good site with a good tutorial on how to draw these charts please post a link.
You people are great.
The purpose of a flow chart is so that you can diagram and understand what you want your program to do.
Is it a requirement? Not for everyone. If its something you think will help you then make one up.
It is definately more helpful in complex programs and/or in programs that have more then one person working on it.
Sorry I don't have any links to tutorials on flow charts.
Edit: Oh and yes, you normally make up the flow chart before coding.
Thantos:
You're great. Thanks alot dude! That is what I needed to read.
thanks m8
Although a flowchart is not critical, I have found flowcharting to be extremely useful.
Mainly, programming comes down to this:
1) You have the internal ability to break processes down to their parts and translate that process into code.
2) You understand your environment (ram, hard drive, application models, pointers, o/s)
3) You have a _thorough_ and familiar grasp of your toolbox (all the C or C++ functions and procedures in your compiler's arsenal)
4) You are a creative (outside-the-box) problem solver.
Where flowcharts really come in to their own is when you use them to analyze a process. Your mind is finite and really can only hold so much. When it is wrestling with a problem, it must hold onto all the variables at the same time so it can "consider" them and keep them ready for use. However, depending on the complexity of the problem, this also takes away processing power from your brain-- it gets bogged down with housekeeping chores. If you flow chart a complex process, it gets the variables out of your head and onto paper. Your mind no longer has to waste thinking power holding onto it and its specifics. Putting things down on paper also forces your mind to think differently, and more critically-- just like discussing something with someone else.
A flowchart is also excellent for finding logic flaws in a process that is not behaving correctly-- you can create a truth table and run your flowchart through the table. It guarantees that you have exercised every possibility that that code will do or can handle.
It means perfect code.
It is not the spoon that bends, it is you who bends around the spoon.
