Looking back at all my posts so far, I have to agree with everything that I wrote except for the post about Why Geeks Need to Know How to Write. The reason being is that, for course materials, I mainly focused on writing about my understanding of the concept and relaying it in terms that someone who may not understand the concept would start to understand.
However, in my Why Geeks Write post, it was mostly my opinions. Now that I have written many slog posts, I can say that geeks need to know how to write because we need to be able to explain complex concepts to those who may not understand them. Take all my other slog posts for example, if someone who didn't know computer science happened to find my blog and started to read it, there is at least a small chance that they will come out having a general idea on what I'm talking about because I have included easy to understand concepts such as diagrams, code, examples, and explanations on why they work or why we need them.
This can also be brought into coding as well. Code without documentation will be useless to others because they will not know what the code does, and they will not want to touch the code either in fear of breaking it. Documentation is essential to a working program because it allows others to understand how to use the code.
I also took a look at my other classmate's slogs and so far we have talked about the same concepts and experiences from course material to assignments and tests. One slog, keirnslog.blogspot.ca/ actually put his lab solutions in his posts which I thought was really interesting because it allows me to see how he implements his code. It gives me a totally different view on how some functions could be done which is really helpful. Also for his post about why geeks write, is very similar to my reason above. Keirn's main point is that we write to clarify things for others.
That's all for this week, thanks for reading.
No comments:
Post a Comment