14 lines
1.0 KiB
Markdown
14 lines
1.0 KiB
Markdown
|
# Technical Writing for the Unemployed
|
||
|
|
|
||
|
|
Unlike most of my other posts which are filled with colloquialisms and a generally casual vernacular this one will not(at least ima try not to).
|
||
|
|
|
||
|
|
## Who this is aimed at
|
||
|
|
<!--- --->
|
||
|
|
<!--- I'm not yet sure if this language is too harsh or unbecoming of the tone i want to give off in this article --->
|
||
|
|
Computer Science students: primarily due to the seemingly enormous lack of communicative tact that way too many students seem to reserve.
|
||
|
|
What I mean is that writing documentation falls unto the typical CS student as being an esoteric, excessive, or otherwise unnecessary task.
|
||
|
|
<!--- potentially shift the goalpost to code instead of general ideology as the structure seems to imply atm --->
|
||
|
|
My theory as to why this is follows: most CS students don't get to experience large enough projects where technical documentation is needed.
|
||
|
|
In conjunction with my theory I propose that large scale projects are exactly what students should be exposed to.
|
||
|
|
This is in contrast to the current method of using smaller unit sized
|