Getting Started with Github as a Technical Writer
Is Github Intimidating?
For the non-technical mind, It is.
Github is intimidating to those of us who have no technical background. Like any new product, Github comes with a set of instructions. Like any new product user, you’ll most likely tick I agree to the terms and conditions and try to do it yourself before failing and finally reading the instructions or Terms of Use.
This is how my journey with Github has Started
Or rather, started. The last time I pushed a read.me document was last year, and it took a whole day to clone repositories, branch off, push commits, merge commits and so on and so forth.
Because I was so new in this technical field, it all seemed so rough, so tough, so out of the flow and so not sexy. My mind was not in sync because I was thrown into the deep end of technical writing and software testing.
This Time, I’m Reading the Instructions
I’m reading Github docs and implementing as I go. I’m also going to be writing about it, implementing and failing publicly. It’s been hard finding a comprehensive resource to learn technical writing. Other than Amrita Ranade on YouTube, there isn’t much for technical writers whose major hurdle is Github.
Like the Comedian Jerry Seinfield, I hope to keep a daily streak in what I do with regard to Technical Writing and Github. For today, I’m following these instructions.
If you have a blank Github profile as I did, today’s assignment is implementing these instructions and overcoming the Github fear.
Become a Medium Super Reader https://medium.com/@sarahngima77/membership (affiliate link — I get a portion of your fee at no additional cost to you.)
