At the start of the year, one of the things in my 'Must accomplish' list was writing a year-in review.

As the year progressed, I had nothing to review in the year. Most people that did year-in reviews got to talk about all the milestones they had achieved in their career during the year.
Seeing as I haven't had the most glamourous career journey this year, I didn't think I'd make it.
However, here I am writing a year-in review about my journey into technical writing, all that I have learnt, seen and felt.

What is technical writing

Technical writing is a form of writing on a specific topic that requires guidance, instruction, or explanation. This writing style serves a unique purpose and therefore has very different qualities than other types of writing, such as creative writing, academic writing, or business writing.

Because of this, technical writing is vital to a wide range of businesses and industries. Without it, complex topics and certain procedures would be difficult—or impossible—to understand or accomplish.

Table of Contents

 1. Why did I start technical Writing?
 2. 10 things I have learnt so far in Technical writing
 3. Conclusion
 4. Call To Action

Today, a year ago, I published my first technical article, and I haven't looked back!
Also, today's exactly one week before my birthday.

Why did I start technical Writing?

• I started writing because I wanted to express myself:
  At the time, I was learning so much and needed a way to keep all the things I had learnt organized and flowing. I ventured into writing.

• I started writing because I wanted to teach, to educate:
  I found out that people enjoyed my writing and also my teaching, so I decided to combine the two of them together into writing technical articles to help developers like myself.

11 things I have learnt so far in Technical writing

• Your first article is probably the hardest article you'd write:
  Not that it'd be difficult in terms of what you have to write, but it takes determination to put yourself out there.
  So, go easy on yourself.

• Just write:
  My rule for a first article is to just write. Start from somewhere, start from anywhere. It doesn't matter that you feel this is a topic everyone has written about, just write. There are people out there who'd need your perspective.

• Don't care about viewership just yet:
  Getting sucked into the pit of, "how many people read my article?" would leave you feeling empty and sad all the time. Just focus on releasing good and quality content. The viewers will come.

• Put yourself out there:
  Write and make sure enough people know that you write. Share your progress with your friends on your various social media platforms. Encourage your friends to share it with their own connections.

• Surround yourself with a community that encourages you:
  This is such a beautiful thing to have as a beginner technical writer. Having people or someone around you to constantly cheer you on, encourage you and give you motivation when you're lacking one.

• Read:
  The more you read, the more you improve your active vocabulary(know the words and terminologies that applies to your target audience). The more you read, the more you know as well.

• Take criticism like a pro:
  It's not fun to think you've worked really hard on a piece, only to have it criticized. However, when someone points out an error in your piece, look at it and take it in your stride. If it is something you need to work on. grow and get better.

note that it is not all criticism that you are meant to work on. Some people project their own personal preferences or choices in the guise of criticism onto people. You should learn how to shut out those voices.

• Review your work before posting!!
  This is something I'm still struggling with, but it is such an important thing to do. You do not want your readers to become uninterested in your work because of grammatical errors or simple coding mistakes

• Be confident!

  If there's a writer to write, then there's a reader to read!

• Be consistent:
  Make sure you set a target for yourself about the consistency you
  want to build, be it weekly or daily or bi-weekly.

  Always show up.

• Have fun!
  There's no point putting in so much effort into doing something if you're not going to enjoy yourself doing it. Make sure to have as much fun as you can while you write and research.

Conclusion

Since putting myself out there and writing, I have been opened to new windows of opportunities especially in mentorship.
More and more people started reading my articles, and reached out to me requesting that I mentor them.
I started from someone who was unsure of herself to encouraging and mentoring people to start on their own technical writing journeys.

After I finished my Learn Front-end web development in 12 days! article series, I got a lot of mentorship requests from people who needed help with their coding journeys. IT was crazy because, all I was doing was sharing what I had learnt?

Technical writing in itself has given me the avenue to EXIST. I get to do the things I love doing (teaching and writing), and help other people find their paths too!

Call To Action

Start today!
Write!
Open an account on Dev Community today, and begin your journey!

What is technical writing?
What is technical writing: Image
Cover Image