I enjoyed David Farbey's post on the name we should call our profession. Aligning our name with the most profitable business model makes sense. If you look at indeed.com for jobs as a "technical communicator," you won't find hardly any. Look for "technical writer" and you find a ton. So what is the benefit of calling ourselves technical communicators, when no one is hiring technical communicators?
Get new posts delivered straight to your inbox.
I'm a technical writer based in the California San Francisco Bay area. Topics I write about on this blog include the following technical communication topics: Swagger, agile, trends, learning, plain language, quick reference guides, tech comm careers, and certificate programs. I'm interested in information design, API documentation, visual communication, information architecture and findability, and more. If you're a professional or aspiring technical writer, be sure to subscribe to email updates using the form above. You can learn more about me here. You can also contact me with questions.