Effective research in technical writing
Tags: writing, productivity
Published: 2020-07-26 20:04:01

Let's say you're writing on a topic which you have little knowledge on. You want to write as much as you can, but your shallow knowledge leads you to draft the writeup until you have 'enough' knowledge. You forgot the research option. In this post, we would learn how to make better research to get more info for our technical articles. So grab some water and let's get started.
![Let us begin](https://media.giphy.com/media/Y1qdgBqNxCc49sbxiB/giphy.gif)

## An example of research in technical writing
A week after I picked up Docker, I had the basics in my head but didn't want to write an article that looks exactly like the thousands already out there. So I decide to ask key questions such as:
1. What are the pain points that brought about the use of Docker
2. Is Docker actually important to everyone
3. Why should I even care?
To answer those questions, I had to do some research. I read blog posts that answered those questions. Then I used the gathered knowledge in my writeup.

This example applies to other technologies. Doing this research helps you learn more about the topic at hand instead of having to wait for a few months when you've become 'an expert.

## How do I research then?
I'm glad you asked. I had to research this myself. I got some info from [College info geek](https://collegeinfogeek.com/how-to-do-research/) and [Bolaji Ayodeji's blog](https://bolajiayodeji.com/how-to-ask-effective-questions-a-practical-guide-for-developers-ckaezf8w004ewc5s1gnkd5puf)
The first is ideally meant for academic research, but there were takeaways.
1. Refine the topic: We may need to scale down on what we are writing on
0. Find key sources: This could be popular blog sites like CSS-tricks, Digital Ocean and Freecodecamp
Here are the takeaways from Bolaji's post on asking effective questions:
1. Use better google queries, adding keywords and sites names. Like this `css specificity site:css-tricks.com`
![CSS Specificity](https://dev-to-uploads.s3.amazonaws.com/i/2f4ndd14x8ymts2ly21k.png)
2. Ask questions on dev communities such as Stackoverflow, freecodecamp or even Twitter. You could get more info for your post.

I did a variation of this some time ago. I requested some help from [Didicodes on Twitter](https://twitter.com/Didicodes) to post a dev poll I could use in [my article](https://dev.to/vicradon/taking-tutorials-doesn-t-make-you-a-noob-41be). My post was more complete with that tweet. I'm grateful for that.

So, now we have learned more on effective research for technical articles, we can then write a killer post by:
1. Writing content
0. Linking to other posts on the topic
0. Adding quality images from [Pexels](https://www.pexels.com/), [Unsplash](https://unsplash.com/), etc. I use [Canva](https://www.canva.com/) for my covers
0. Adding memes once or twice
0. Adding content like StackOverflow answers, tweets, etc if necessary


## Wrap up
You have learned the basics developer/technical-writer research in this post. Here are the key takeaways:
1. Know what you are writing on
0. Write within your current knowledge
0. Ask some key questions
0. Get answers using advanced search tools 
0. Use the new knowledge to write more content that would make your post relevant

Share this article if you found it useful. Please, leave a like (or multiple). Adios ✌🏽🧡

## Attributions
1. [Bolaji Ayodeji's Blog](https://bolajiayodeji.com/how-to-ask-effective-questions-a-practical-guide-for-developers-ckaezf8w004ewc5s1gnkd5puf)
2. [College Info Geek](https://collegeinfogeek.com/how-to-do-research)

![The end](https://media.giphy.com/media/APHFMUIaTnLIA/giphy.gif)