Today is the first day back after half term - player Danny has joined the game with full battery. This morning for starts with the class looking at Small Basic to warm ourselves up and get back into the flow of coding. We coded the program to instruct the user to name each days of the week. Thus, we stored the data into an array. I had difficulties at the start as I was uncertain about iterations and arrays overall due to its complexity. Later on, after "Jovial John" revealed his way of doing this task, and I then learnt how he did it by reading his example. I believe my method of improving is to re-read code examples.
Next, "Jovial John" gave us instructions to type the definition of the 'quality of code' and 'readability' in a word document without our names. Then we were commanded to print it. This is to recap our knowledge on these two important topics as well as to test who is listening to instructions. As a result, some people within the class made errors and put their names, as well as not proof reading. When printed, "Jovial John" divided our definitions up and split us into groups to judge which definition is the best. Luckily, mine got returned to my group and was voted the better definition of the others because I included examples in a good layout (bullet-points) . In the end, "Jovial John" proudly read my definition. During so, I noticed one grammar mistake.
Afterwards, "Jovial John" wanted to know everybody's issues within A1, A2, and A3. To do this, "Jovial John" linked us to an interactive online whiteboard where we posted notes upon our uncertainties. Furthermore, after a long half term break, I generated a few uncertainties about pseudocodes and flowcharts. This was a fun task because some people put Brian the dog in a banana suit from Family Guy. "Jovial John" listed down all the problems we had, and helped us in groups or individually based on the amount of people who requested it.
Whilst waiting for help from the master, everyone created a flowchart for making a cup of tea. In this case, everyone did it differently and in different order. This means that there are no wrong or right as things can be worded uniquely. This was to also help practice our understanding of A3T1. I had no problems with flowcharts so this was a good thing for me! (We did this on Gliffy and Draw).
After lunch, "Jovial John" helped the people including me who were stuck on pseudocodes. We started off with a very easy example and then did one slightly harder. One main issue was my poor understanding of the statements such as 'OUTPUT' also meaning 'WRITE'. However, "Jovial John" cleared it up for me simply within a few sentences. Additionally, I went back to the pseudocodes I attempted on A3T1 and improved it a lot using the help obtained. Moreover, whilst working I helped other students around me as I have finished A2.
 |
| Pseudocode Practice |
Check out the official Develop Banter page on Twitter: https://twitter.com/
 |
| Billy LAD 1 |
 |
| Billy LAD 2 |
