- As I am not currently working in a school, a group of academics and I had a look at the Snake task and the implementation process and the difficulties we faced with out own style. As most of us had previously done coding, we talked more about the implementation process itself
- Firstly, there was definition of the problem
- Instead of going “this is the problem”, we took the approach of finding out other solutions to the problem and discussing why those were not sufficient, or how they did not satisfy the customer
- Secondly, there is planning the solution
- Pseudocode is the biggest help when it comes to planning a solution, and I would highly recommend using a whiteboard to plan as mistakes can be changed. Another hint would be using magnets too, as permanent pieces that are key to the process can be moved around
- Flowcharting is the next step after pseudocode as it allows a visual view of the process. Once again a whiteboard was used to visualise the solution
- Thirdly, coding the program
- We rushed through this step with multiple people working on different parts of the code. This was difficult at first because we were changing what variables we were using. However, once we determined what our global variables were and what style of coding we were using the process came quite naturally.
- Next came the testing
- How we did this was one person running the program and the rest of us taking notes as to what we thought needed perfecting. After a certain amount of time we went around and made sure that all the solutions were unique, took turns implementing this in the code and repeating the process.
- This whole time there were comments being made in the code as to who was coding what part and what each part did so that if a third party came along, they would see what we each did.
You must log in to post a comment.