Geeks should know how to write because communication is a key tool in a business environment. For example, in CSC108 we learned how to write out structured docstrings. These docstrings will prove to be very useful when a peer in the workplace wants to learn more about your program. In addition, the use of comments within code also aids peers as they navigate the inner workings of your code. The need for communication has already been highlighted by group assignments, within which a great amount of time is spent sharing ideas and working together on a communal program file. When a computer scientist enters the job market the possession of great communication skills, especially those concerning text based communication, are looked very highly upon by employers. Due to the abstract nature of their work, computer scientists need to be able to effectively communicate their ideas with their peers to make sure everyone is on the same page when working to complete a project.
Geeks also need to know how to write because a clear and comfortably-used program is highly important to a user. In today's society it is important to make technologies easily understandable and user-friendly, the use of textual communication plays a key part in simplifying a user-interface. Many programs have some sort of "help" page in order to instruct the user on how to operate the program. The instructions on this help page need to be exceptionally clear or else the burden on the user will increase, therefor it is necessary for the "Geek" that is writing the help page to be able to clearly define all important aspects of the program as well as how to navigate through the user-interface. lowering the burden on the user is great way of ensuring a program is used properly and comfortably, a geek should know how to write for this purpose.
