As my Web site explains, I am a technical communicator, which by definition means I wear a lot of hats: writer, editor, information architect, Web designer, etc. It’s a lot more than technical writing. In fact, I’d argue that tech writing is just one thing that technical communicators do. Check out STC’s Web page to read more about what technical communicators are and what they do—they sum it up quite nicely.

The obvious advantage of this profession is being able to explore a lot of cool ways to present information. The disadvantage is occasionally having a minor identity crisis when it comes to explaining your role. More about this in an upcoming blog.

I’m not going to write a blog every week, as I don’t think that’s how they are intended. Just random and/or timely posts about what’s going on in STC, projects I’m working on, and the every day (very exciting) life of a technical communicator.

If you’re interested in a career in technical communication, specifically in technical writing, check out this dude’s blog. He provides some high level information about types of tasks tech writers perform, common industries to work in, contract vs. salaried pay, and so on. Although he doesn’t come out and say you need a degree in technical writing, he basically says you’re going to need some technical aptitude and knowledge of common tools such as RoboHelp, Framemaker, InDesign, and so on. So don’t go get an English degree and expect to write documentation for IBM any time soon. ;)