- Identify what you are trying to do.
- Ex: are you trying to convert pounds to ounces, are you trying to reverse a string, are you trying make a object move back and forth on the screen, etc
- Figure out how to do that or plan the solution
- In my experience you do this in a flow chart, puesdo code or both, although depending on how simple what your trying to do is it might not be necessary
- For more complex programs its helpful with making sure you plan for all the different cases in which your program may be used
- Code the program and decide the language you are using
- This may include looking up ways to do what you planned in the previous step in the language you choose.
- Test and debug your code
- In this step you are basically making sure it works in a variety of cases, if your practicing on a website, they do the testing part for you.
- If your not on a website practicing this involves coming up with test cases and figuring out how to see if it is correct.
- Documenting
- For me this normally involves commenting what things are suppose to do , but normally for me its a program for personal use.
- If its for a company or something it would probably include, the origin of the problem, a description of the program, the psuedo code and/or flow chart, data-record descriptions, a list of all the programs involved, testing results , and commenting on what stuff is suppose to do.
- This step should really be done throughout the creation of the program.
A example of this process is in this video which will done using CodeWars, cause I didn’t want to come up with a problem, or tests, I also will only be commenting for documentation.
Code blogger 