Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

71%
+3 −0
Q&A Technical Writer Skill Set

Monica covers the main points excellently. Beyond that, if there is one specific thing I would suggest that you do to improve and remain relevant as a technical writer, it is learning to code. Thi...

posted 3y ago by Mark Baker‭  ·  edited 3y ago by Mark Baker‭

Answer
#2: Post edited by user avatar Mark Baker‭ · 2021-01-22T13:47:17Z (about 3 years ago)
  • Monica covers the main points excellently. Beyond that, if there is one specific thing I would suggest that you do to improve and remain relevant as a technical writer, it is learning to code.
  • This is not about reading source code (though that is a useful skill in some jobs) nor about writing code yourself (though you won't learn unless you do), it is because everything these days runs on software. There will be code almost everything that you will document. And the reason it is useful to know how to code is that it will help you ask good questions of developers so that you don't waste their time, and so that you more readily understand their answers, and the way they think.
  • Developers are critical path on every project, so you will get more respect and be more valuable if you don't waste their time. And they will be more willing to give you the time you do need if they respect you and feel you have done your homework before you ask your questions.
  • You certainly don't need to know how to code to have a tech writing career, but it will open additional doors, and, beyond the basics that Monica mentions, it is one of the best things you can do to stay relevant and enhance your career.
  • Unless you have a reason to choose something specific, the language to learn on today is probably Python. But don't think of it as learning Python. Think of it as learning to code using Python. And no, learning HTML is not learning to code.
  • Monica covers the main points excellently. Beyond that, if there is one specific thing I would suggest that you do to improve and remain relevant as a technical writer, it is learning to code.
  • This is not about reading source code (though that is a useful skill in some jobs) nor about writing code yourself (though you won't learn unless you do), it is because everything these days runs on software. There will be code in almost everything that you will document. And the reason it is useful to know how to code is that it will help you ask good questions of developers so that you don't waste their time, and so that you more readily understand their answers, and the way they think.
  • Developers are critical path on every project, so you will get more respect and be more valuable if you don't waste their time. And they will be more willing to give you the time you do need if they respect you and feel you have done your homework before you ask your questions.
  • You certainly don't need to know how to code to have a tech writing career, but it will open additional doors, and, beyond the basics that Monica mentions, it is one of the best things you can do to stay relevant and enhance your career.
  • Unless you have a reason to choose something specific, the language to learn on today is probably Python. But don't think of it as learning Python. Think of it as learning to code using Python. And no, learning HTML is not learning to code.
#1: Initial revision by user avatar Mark Baker‭ · 2021-01-20T04:51:49Z (about 3 years ago)
Monica covers the main points excellently. Beyond that, if there is one specific thing I would suggest that you do to improve and remain relevant as a technical writer, it is learning to code. 

This is not about reading source code (though that is a useful skill in some jobs) nor about writing code yourself (though you won't learn unless you do), it is because everything these days runs on software. There will be code almost everything that you will document. And the reason it is useful to know how to code is that it will help you ask good questions of developers so that you don't waste their time, and so that you more readily understand their answers, and the way they think. 

Developers are critical path on every project, so you will get more respect and be more valuable if you don't waste their time. And they will be more willing to give you the time you do need if they respect you and feel you have done your homework before you ask your questions. 

You certainly don't need to know how to code to have a tech writing career, but it will open additional doors, and, beyond the basics that Monica mentions, it is one of the best things you can do to stay relevant and enhance your career. 

Unless you have a reason to choose something specific, the language to learn on today is probably Python. But don't think of it as learning Python. Think of it as learning to code using Python. And no, learning HTML is not learning to code.