Discussion Posts responses should be 150-200 words

Assignment responses should be 150 words

Discussion Post directions : Discuss the importance of planning out a program on paper before writing the actual code, and why there are advantages to doing it this way.

posted by Damon:

Programing is complex, in itself. Much like anything else that may be complicated, breaking down a process via writing it down will save a great deal of time, and errors. In the heart of workshop, this process can fall easily under the phrase “Measure twice, cut once”.

Planning out a program allows the programmers to see what should be executed, from start to finish. This represents how a program should initiate, what modules may be useful, how many steps will be required to do the task, and eliminate useless coding. This can eliminate the potential spaghettis coding, by writing down the step by step process. It is easier to create the flowchart and prepare modules based on said flowchart, compared to writing code as you go. Instead of going back and forth fixing codes that you already completed, concentrating on the steps already written out will allow you to write the correct codes, and flow directly into the next part. Preparing beforehand can also give a programmer a chance to use already existing modules that have been tested to work. I find the idea of programming without preparation panic inducing, and would only lead to messy codes. I do not have much experience in coding, but when I think of freehanding any of my crafts, I always spend more time preparing and laying the foundation of what I will do, than the actual execution of it.

It’s also neater, more efficient, far more professional, and proven to be the status quo. It works best to prepare beforehand, and then execute after. Measure twice, cut once.

Posted by Elmer:

Spaghetti code is not good for programming, but when you think about it before you even use a flowchart to document the process, you use spaghetti code in a verbal since when you brainstorm a program that you want to create based upon ideals and thoughts of how to make this program become a working peace of art. When you have established that you lay out a flowchart and clean up the spaghetti to make the flowchart into a structed chart of steps to code and put into a program you may start with a sequence structure and continue to document the flow of that process of the program then you will add some additional flow charting symbols to your process such as selection and decision structures. Programming is a thinking process and requires a visionary to understand processes and as you continue with the process of verbal brainstorming with spaghetti code you will need to add a loop structure to the chart to decide to continue or repeat the previous process if you are working for a company you may be working on a module within the overall program which could be nested or stacked with another structure of the program. I had a position working with statistics and working with spreadsheet that involved and lot priming input of data to get the results we needed using that priming input into a program is great for games or guessing programs. I do feel structure is very important in a program to make a clear set of instructions for the other programmer to step into a process and know how your coding will fit in or take someone else’s module and place it into the program.

Assignment 1.2 Directions: Draw a structured flowchart or write pseudocode that describes the process of guessing a number between 1 and 100. After each guess, the player is told that the guess is too high or too low. The process continues until the player guesses the correct number. Pick a number and have a fellow student try to guess it by following your instructions.