My Journey as a Technical Writer.
How and Why I started writing articles and become a novice technical writer.
Hello World! I am Meet Gor, a self-taught web developer, Linux enthusiast, and a newbie technical writer. I am currently studying in an Engineering college pursuing my B. Tech in I.T. I love to explore new programming languages and technologies, create innovative projects, love to write stories and blogs like this.
How it started
When I was learning Vim, I found the need to write some kind of cheatsheet for myself. So I started writing it, soon I realized I had written a kind of an article instead of a cheatsheet XD There were a lot of chunks of it unorganized but meaningful in some sense. So, from there I started to research on article writing. I found the term perfect for my techno feelings to express i.e. "Technical Writing". I soon landed on Hashnode, I knew Medium, GeeksforGeeks but found Hashnode absolutely perfect and much more viable to the creativity of an author.
Starting on Hashnode
My first article was published on Hashnode, which I absolutely love and adore. That was a bit big article about 12 minutes for a beginner me writing everything about Vim which I knew about that time. The response was not that bad, I received a couple of reactions and comments to pump me up but I never felt confident to write more articles.
Until I found an Internship at GeeksforGeeks for a Technical Writer role. Geeksforgeeks is a start-up for Computer science students to learn and grow with free as well as paid courses and mentors. In a couple of months, I wrote some 10-12 articles about Shell scripting. There I really found my interest and the confidence I wanted. It was really a great experience working here and loved the freedom it provided to the authors with genuine and constructive feedback along with a decent stipend. Here you can find my work.
The start of the
Soon, on June 6th something stuck in my mind that I should write about how to use Vim for doing various things. So, the first idea was what currently I was learning in College i.e Python, I started writing about the Vim set up for python and I completed it within 2 hours. I published it on Hashnode and from there I never looked back. I started writing an article every 3-4 days. That summed up for 3 months making 21 articles till September. I also made my personal open-source blog called
Techstructive Blog using Jekyll and hosted it on Github pages.
I did experiments with a lot of blogging tools and frameworks like Netlify with Flask, Django distill, Gatsby Js, etc and finally landed on Github pages with Jekyll as it is quite customizable and a lot easier to add certain components as well.
Why I kept going?
It's not hard to keep up with what you love to do. Even if you are not that interested in doing something, just having curiosity and consistency can turn any work into a skill. Here are the reasons why I love to keep going as a Technical writer ( some of them are from the Bootcamp session from Edidiong Asikpo and Quincy Larson :)
- Over a span of 5-6 months I have learned a lot than I had in my past 2 years, I understood that I am writing for myself first and not only for other people.
- It helps me in improving my online presence and clearly showcases my skills and interests.
- Able to sum up ideas and document them well.
- Maintain a record of learning for your future self.
- Learning to get things done by writing articles consistently in an allotted time.
How I kept going?
I am writing articles almost daily one for my blog and another day for GeeksforGeeks. I have a schedule and follow it almost punctually. I have never run out of ideas and motivation till now, every time I feel that there's no motivation in me, something or the other pops up just like this Hashnode Bootcamp - The Art & business of Technical writing. Some youtube videos, Hackathon, Bootcamps, Project, conversations with friends just can impact in a constructive and a drastic way, they create a refreshed experience and allow you to clarify the doubt in yourself. Just you have to be open to ideas and feedback from other people and learn in harmony.
My writing workflow
This is really a neglected part when you ask a technical writer as it can really improve your productivity. I use Hashnode and Vim both for writing out the markdown script. I like to write the subheadings or the content which I want to explain in that article. That really makes a bigger idea in a small chunk and I repeat the process until I feel that is the lowest abstracted way I can explain something. I record some screencasts in gifs on ScreenToGif recorder, MS Paint and Canva as an Image editor, Hashnode makes uploading and accessing images, gifs so easy and it's quick too, really Hashnode is just flawless for a tech writer.
That's been my story soo far. I have grown from a noob coder to a somewhat confident nerd who can quickly write functional scripts, jump in Vim with more speed, and of course, teach someone something that can be helpful. It also is a way for me to relax and enjoy the process of programming.
Thanks a lot if you have been reading till here. Thank you Hashnode for providing such a great opportunity to create a side hustle here. As always Happy Coding :)