Technical Writing


Why Technical Writing? Isn't that shit boring?

I chose to become a technical writer because I accidentally figured out that I was good at it. You see upon researching finding ways to become self-sustaining with my new found love for writing, I began deep-diving into ways I would be able to use writing to get a decent job. Something that would provide enough for me to live off of, but also allow me to be able to work on creative writing projects as well. And it was a bonus for me that technical writing was still a form of writing and that I would be able to enjoy this were I able to get a job as a technical writer.

After figuring out what technical writers actually do, I realized that I've had this ability all along. I previously used to be a software developer, and while I still dabble with code in order to try and keep my mind sharp, I left the industry due to wanting to pursue more creative ventures. But during my time as a developer, I would write documentation that would explain what the code was doing, but also have to write documentation as to what the program itself was doing from the perspective of the user and how to use it. During that time, I also had exposure into help-desk and supporting users with daily computing tasks and emails.

I had a knack for being able to explain complicated items to users very easily. Sometimes, it was just explaining only the bits that the users needed in order to do their jobs, but without all the crap that would end up confusing or intimidating them. Other times it was by using analogies that I would make up on the fly in order to get them to understand what it is that was actually happening so that they could intuitively use the piece of software, but begin exploring the software on their own without having to follow a rigid step-by-step instruction, and if something went wrong, they wouldn't be able to figure out what the problem was. Where as having a intuitive understanding of what the program was doing, they might be able to troubleshoot some portions of the program themselves and only call help-desk due to actual technical issues.

My end goal was always to make every user self sufficient enough so that their need for calling the help-desk was at an all time low. And to top this entire discovery process off, I enjoyed the hell out of it. There was nothing like the spreading of a smile across a user's face when the light-bulb went on and they finally understood the thing that they had been beating their heads against for so long.