This morning was a different approach as we didn't code, instead "Jovial John" talked about methods of testing programs, such as validation. The important ones were black box and white box. Black box is invisible, meaning you test the program as a whole to find errors and problems. Whereas on the other hand, white box is when the programmer looks into a chunk of code specifically with more detail. These two ways are methods students like myself can use when we test our future programs.
Afterwards, we were instructed to test a specific program made last year by another student. We had to find its general assumptions and errors. As a result, I found a wide variety of errors and problems within the validation of the wall height/length. I've taken this into account and consequently will try to make my program more robust and reliable in future.
Just a side note, Alex S arrived to the center later than usual with transport issues. However, this meant he had to either do 75 push ups or sing Miley Cyrus' Wreckcing Ball. He chose the short but brave route and sang the song, it was a good laugh! Around the end of the day, Gabe H was punished by wearing a "LATE" hat. =D
Subsequently, today was a focused day on continuing and hopefully finishing our pseudocodes and flowcharts. Each student did which was easiest to them but I had already finished my pseudocodes at home and improved it last night. "Jovial John" noticed that Matt T was also done with this pseudocode, so we worked together and peer assessed each other's work and chose to continue flowcharts later on the day. We peer assessed our work using the specification we printed off - we discussed how we would make it efficient; if the general assumptions match the code; and corrected all spelling/grammar mistakes along the way. During so, I learnt that I forgot some major detail in my code, therefore I got support from Matt T and added it in. Eventually, everyone did the same and swapped every 30 minutes until the end of Lunch. This should be beneficial as it allowed us to share and spread intellectual knowledge. Overall, this helped me a ton!
Moving towards the end of the day, "Jovial John" moved on and discussed with the class about different ways of making our programs effective, known as the "coding guide lines". The main one "Jovial John" wanted us to be aware of was CamelCase within good variable names. Lastly, after all the work of pseudocode, I used it to help me create my flowcharts. As a result, I am now approximately 30% done, and should be reaching near the end when I get home.
In conclusion, today was a good day to get myself even more focused than before.
Check out the official Develop Banter page on Twitter: https://twitter.com/
No comments:
Post a Comment