So much of my job as a technical writer is spent finding mistakes. And yet, when you ask Google what the most important skills are for technical writing, you will be told things like "ability to write" or "familiarity with technology". Those aren't wrong, but they ignore something very important.
I have been listening to a lot of non-fiction audiobooks lately, but this one was of special interest. In part because I could be described as 'going solo', but also because of the relationship between living alone and the design of cities (and I have a bit of a passion for urban design).
Ever since I was first introduced to academic research, I have always questioned why academic writing must be so complex. In this post, I explore and reflect on some of the possible reasons for its complexity. I also discuss knowledge translation and plain language writing.
Process mapping and improvement are some of the most important skills you can develop in a typical office-style workplace. Because without them, productivity can be greatly reduced. This post exemplifies that with a story from my workplace. But the TLDR version is: use process mapping.
I recently finished an online 6-week technical writing course through a local university. In this article, I talk about whether I found the course valuable, and if I think you should enrol in one.