Wednesday, January 21, 2015

Week 3 Why geeks should write

This is my first slog for CSC148. Most of friends who took this course last year told me that CSC148 is very hard and even harder than 200-level CS courses. However, I feel excited about upcoming challenges.

Keeping Track of Mistakes for Future Use

By recording what happen in programming, geeks can easily keep track of what they think, what difficulties they encounter and how they solve them. Especially, recording mistakes is an important approach to preventing from making same mistakes in the future. It is very likely that geeks may face same problems in some other projects. Instead of resolving the problems, it is a efficient way to refer back to the journals that geeks write and find solutions in the journals. Geeks cannot remember every single detail of codes; therefore, journals will help geeks program.

Sharing Feelings with Other Geeks


Journals that geeks write can be used as sources to share experiences with other people, such as geeks, colleagues, and someone who shares same interests in programming. Sharing could simplify working load and increase efficiency, since reading other journals could help geeks find others' advantages and apply these to their own work. Writing journals is an effective way for geeks to communicate their thoughts, feelings and opinions.

Educating Next Generation
descendants could learn by reading journals which are written by previous geeks, and revise it during their work. By accumulating the rich experiences, they could pass these down to next generation in order to train new geeks.

 




No comments:

Post a Comment