Technical Writing for Developers: Difference between revisions

From Federal Burro of Information
Jump to navigationJump to search
(Created page with "Just be cause to instruct computers to do your bidding all day doesn't mean you should not spend some time learning how to communicate iwth humans well. This is an opinion pe...")
 
No edit summary
Line 1: Line 1:
Just be cause to instruct computers to do your bidding all day doesn't mean you should not spend some time learning how to communicate iwth humans well.


This is an opinion peice. It's a collection of my opinions.
aka "Tech Writing for Devs"
 
Just because you instruct computers to do your bidding all day doesn't mean you should not spend some time learning how to communicate with humans well.
 
This is an opinion piece. It's a collection of my opinions.


This is a collection of notes about how to write well for those of us in Information Technology.
This is a collection of notes about how to write well for those of us in Information Technology.


This doucment is therapy for all the shitty stuff out there that will never be fixed.
This document is therapy for all the shitty stuff out there that will never be fixed.


# Documentation - Who, Where, and When
# Documentation - Who, Where, and When
Line 13: Line 16:
Yes.
Yes.


Different places and forms of documenation are appropriate and effective for different projects.
Different places and forms of documentation are appropriate and effective for different projects.
 


# Acronyms
# Acronyms

Revision as of 14:18, 19 May 2022

aka "Tech Writing for Devs"

Just because you instruct computers to do your bidding all day doesn't mean you should not spend some time learning how to communicate with humans well.

This is an opinion piece. It's a collection of my opinions.

This is a collection of notes about how to write well for those of us in Information Technology.

This document is therapy for all the shitty stuff out there that will never be fixed.

  1. Documentation - Who, Where, and When

Should I document in code or in a wiki page or in a read me?

Yes.

Different places and forms of documentation are appropriate and effective for different projects.

  1. Acronyms

You should use them , but not too hard, and you should follow some guide lines.

The art of writing is quite old and is employed by various fields. Each field has it's own uances.

Some places you might look for gu8delines are:

  • Legal Writing
  • Acedemic Writing
  • Scientific Writing