Thursday, 23 October 2014

Always Refer To The "Expert"

Good Afternoon,

This morning, we went straight into the Thursday Quiz Sami H made. It was about a project called 'inForm', where the coding and programming are very advanced. Out of 10 questions, I got a total of 4 as it is incredibly difficult due to the fact that most questions were focused visually on the video, rather than what it was talking about. As a result, Joe B, Ben C, and Liam B were the top three winners, decided by guessing games and rock paper scissors!

Afterwards, the whole class did a group task "Jovial John" promised a few days ago. The class split up into three distinct groups as there are three unique table sizes. My team leader (Adam M) was given a specification via email which told us the instructions to what to do. We had to create a flowchart, pseudocode, and re-type a neat specification about the process of a greenhouse maintaining its temperature to 28 degrees Celsius. We split the team into three groups based on our best knowledge. Myself, and Adam M, Ashley P, Euan J, and Ben R all focused on the flowchart. What was challenging was the part to simplify the process, therefore allowing others to understand it more easily. On the other hand, Matt T and Billy B focused on the pseudocodes, whereas Alex W and Tom L were helping. Moreover, as an extension, my part of the group created a separate flowchart of the process of watering/misting the plants within the greenhouse at a specific time of 8am and 6pm. It became much easier as I practiced more. In the end, our group won with a total of three points, putting the other groups behind by one point and two point five points. However, our group didn't have the best specification, nor did we have the best communication skills. This was because we had a poor start when choosing our roles. However, we did have the best flowchart and pseudocode, which I am very proud of!

Moving on, "Jovial John" showed us a video of a business meeting, where many people would always refer to the "expert" when they don't know what is going wrong. It was a funny yet a strong message. It was able to inform many others about communication and assumptions. This woke us up and allowed "Jovial John" to explain the details of A3's tasks. At first, I was very stuck once again as there was a lot of information to take in at once. However. after asking for help from "Jovial John" and from others around me, I got the hang of the task and worked on A3T1, where I had to create a document of specifications. These included: Assumptions, inputs, processes, and outputs. This is to help our future program and acts as a 'to-do list'. Furthermore, "Jovial John" gave us some examples from students in the previous years, which helped me improve my work even more overall.

During self-study, I finished the specifications and planned out my to-do list for when I return home. I planned it out by looking at the priorities, which is to get the last slides A2T1 finished, start A2T2, and proof read A3T1. Today was another fun day as I really do enjoy stepping out of my comfort zone, then improving and achieving something important under pressure. It's a great feeling!

Check out the official Develop Banter page on Twitter: https://twitter.com/DevelopBanter
Jovial John LAD 14

Jovial John LAD 15