I am a technical writer. If you don't know what a technical writer is, then here's what I do: I convert complicated concepts and processes into easy-to-read written descriptions and procedures so that you can quickly figure out what you need to know.

I've worked in safety controls and healthcare and have written and edited a wide variety of documents, including user's guides, knowledgebase articles, customer notifications, training materials, and blog articles. An exciting project I have right now is creating documentation completely from scratch for parts of a web-based practice management system. That means I have the joys and challenges of structuring a new document, interviewing subject matter experts, and writing documentation so that clients can easily understand the program and save countless hours that they would otherwise spend trying to figure out the program by themselves.

I really enjoy technical writing. In fact, writing technical documentation is like solving a mystery—you get to research, talk to different people from different departments, mull over facts and conjectures, strategize on the best way to present and structure information, reconsider everything you've written, and then lean back and smile at your tidy, complete masterpiece. If technical writing was a TV show, it would be called Technical Documentation, She Wrote.

In addition to writing technical documentation, I also love reading books, discussing both the correct and evolving usage of grammar, and listening to vinyl.