DEV Community

Cover image for A Brief Introduction to Technical Writing

A Brief Introduction to Technical Writing

Stephanie Morillo on August 09, 2020

Image credit: #WOCinTech Chat Technical writing impacts every developer. They consume content written by technical writers in the form of document...
Collapse
 
tomfern profile image
Tomas Fernandez •

Great post! Thanks for the recommendations!

I'd like to add two resources that, while not specific to technical writing, have helped me a lot:

I've posted a bit on why I chose technical writing as a full-time job and why I like it:

Collapse
 
momin profile image
Md Abdul Momin •

I got the course on Lynda! Thanks

Collapse
 
radiomorillo profile image
Stephanie Morillo •

Great, thank you for sharing!

Collapse
 
dougaws profile image
Doug •

I've been in the technical writing field for over 30 years, mostly working on API documentation. My criteria for good API documentation are simple:

  • Is it accurate?
  • Is it complete?
  • Is it necessary?

Accuracy is paramount. If you incorrectly describe an argument as a 64-bit integer, but it's actually a 32-bit integer, you lose your audience.

Completeness is crucial. I hate it when I read an API doc and they fail to give me details of possible error/exception conditions. So this takes a string? How many chars? Min? Max? Does case count? Unicode?

Don't litter a technical doc with sales/marketing blather. I don't care if it's the greatest thing since bottled beer, let me decide. Keep the conceptual stuff in a separate section, as if I care. Don't make me wade through a bunch of new terms you heard on a TED talk. Use industry-standard terminology.

Collapse
 
steelwolf180 profile image
Max Ong Zong Bao •

To be fair I think spending time to write constantly helps alot. While devouring the book like "On Writing Well" is really a good reference point.

Collapse
 
radiomorillo profile image
Stephanie Morillo • • Edited

I didn't argue to the contrary! ;) Like any other skill, technical writing requires a lot of consistency and repetition to get good at it (as you point out). But as you imagine, there's more to writing than "sounding good" on a page, and that's an important thing to highlight—technical writers care about the user experience and their skillset reflects that! :)

Collapse
 
dougaws profile image
Doug •

If you want to be a good writer, find a job where your work is reviewed by an editor. I still get dinged every once in a while for some sloppy passages.

Thread Thread
 
radiomorillo profile image
Stephanie Morillo •

100% this. Working with editors is the topic of my next newsletter.

Collapse
 
mrsaeeddev profile image
Saeed Ahmad •

Hey Stephanie,

Great guide for anyone who wants to break into technical writing!

Thanks for writing this.

Collapse
 
radiomorillo profile image
Stephanie Morillo •

Thank you, Saeed!

Collapse
 
andrewbaisden profile image
Andrew Baisden •

Great guide lots of reference material thanks for sharing.

Collapse
 
radiomorillo profile image
Stephanie Morillo •

Thanks for reading, Andrew

Collapse
 
formicidaemate profile image
Benjamin Saul •

Thank you for the sharing this. I am going to reference this going forward.

Collapse
 
radiomorillo profile image
Stephanie Morillo •

Thanks Benjamin!

Collapse
 
meghna__das_ profile image
Meghna Das •

Perfect overview of this amazing career field. Thanks for sharing!

Collapse
 
vadoverde profile image
Sam Mourad •

Comparing to recipes and the idea of concise and precise is very helpful. Thanks for the article.

Collapse
 
radiomorillo profile image
Stephanie Morillo •

Thank you!

Collapse
 
noman1981 profile image
noman mazher •

awesome