SLOG 9: Revisiting SLOG 1:"Why Geeks should Write"

Hi All!!!
I am back with another exciting entry for CSC148. I have to say, these weeks seem to be going by super fast. It sure seems like we are on a fast forward mode. Regardless of that, lets take a moment to look back to the earlier weeks of the semester. In particular, let look at SLOG1: "Why Geeks (Computer Scientists) should write?"
First and foremost, I want to look at this SLOG particularly because the whole point of us being required to write slogs in my opinion is to see how helpful writing about a topic is. In my previous slog if you remember I mentioned that writing is helpful because since computer programming is a different language, translating material from that language into English/ non-computer programming language can lead to better understanding of the material. I have to say, this is actually True as writing SLOGS and summarizing the material learnt in class helped me to understand it 10 times more than it would have if I had just practice writing the codes. It not only helped me to understand the material but it also helped me to remember it. As I am a cognitive science major, a little connection has to be made (just like in my first slog): translating the programming material into English and English material into programming codes literally coded my neurons (brain cells) in such a way that certain material such as the __init__ method, class and subclasses, the special methods __eq__, __str__, and __repr__ became a default for me. When I was starting to learn these material it was hard to wrap my head around it and now it feels like its no big deal at all. So you can see, writing is helpful for the writer as it helps them to not only understand the material but also to make their codes more concise. I surely found myself writing more concise codes during labs and assignments once I wrote what needed to be coded in English first and then doing the translation.
I also mentioned that writing for 'Geeks' is crucial because it helps others understand what the codes are doing and what they are suppose to be doing. Some people who are new to programming, like myself, understand what each method does and how to implement it for a particular case but when it comes to reading the code have difficulty understanding what exactly is the code doing. Reading what computer scientists/Geeks have written in non-programming language helps us to understand what their code is doing and how we can actually relate it to our own scenarios.

I am sure you all will agree with me on this that writing the slogs has contributed a great deal towards our understanding of the material. Just a little advice for you and for myself: Look at theses SLOGS before the final exam... It helps to read your own slogs and those of other students as it fills in the gaps of materials and it helps to remember material in concise form.

Thank you all for reading my posts and keeping up with them every week. 1 more SLOG/Week to go... Lets do this guys... Good luck for all your exams and KEEP WRITING!!!