Time for #DEVDiscuss β right here on DEV π
Inspired by @blackgirlbytes's Top 7 post, tonightβs topic is...ultimate tips for writing technical content!
Based on her experience as a Developer Advocate, RizΓ¨l Scarlett has written an incredible, comprehensive guide to writing technical content β seriously, take a look π
So let's talk about it!
Questions:
- Which of the points in the ultimate guide have served you well as a technical content writer?
- What are your top tips for writing technical content? Where or how did you learn them?
- Any triumphs, fails, or other stories you'd like to share on this topic?
Top comments (1)
What are your top tips for writing technical content? Where or how did you learn them?
My answer: Through a few wise individuals in a tech Twitter Space on content creation, I learned that the topics people write about is not always. Creators in some fashion speak out about the same thing. What gets people to read your tech content are the following:
Its presentation
The level of popularity you have (this can be debateable)
Which of the points in the ultimate guide have served you well as a technical content writer?
My answer: Writing tech blog posts is only one aspect of writing tech content. It's important to have some form of knowledge on how to maintain a product's documentation. Note: I am aware the focus is on writing technical content, but I've noticed and used to think that creating technical blog posts is often seen as the only way to gain experience to become a technical writer.