I usually don’t talk about journeys unless I’m describing actual travel. But I have to admit that co-founding DMN Communications and becoming a tech writer for hire has been a journey. In fact, several related journeys. One of learning, one of becoming more fulfilled in my career, and one of finding out what I’m capable of.
While not all of the journeys I listed in the last paragraph are complete, I’m definitely making progress on those roads. But there’s more to my freelancing than the journeys.
Becoming a full-time freelancer has changed me. In a number of ways, and all of them good. At least I think they’re good … Curious? Read on.
When I gave a talk about FLOSS Manuals at FSOSS 2010 in October, someone in the audience asked a question I definitely wasn’t prepared for. And I was asked a similar question a couple of times during the event:
Does FLOSS Manuals drive people away from the official documentation?
I tried to explain that explain that one of the goals of FLOSS Manuals (at least from my perspective) is to get people up and running with whatever technology quickly and in a very friendly way. But those manuals don’t cover everything – they get you going. If you want to delve deeper into the software or technology, the official docs are still there.
While that seemed to get some folks more interested in FLOSS Manuals, the question illustrated something of a gap in perception, on my opinion. I don’t think it’s FLOSS Manuals vs. the official documentation or other documentation or sources of information.
I mentioned this to Adam Hyde, the head honcho of FLOSS Manuals, and he’d never been asked that question before. Adam asked me to start a discussion on the FLOSS Manuals mailing list. That posting prompted a lot of interesting responses. You can read the thread, starting here.
But that discussion also got me thinking about this in the context of documentation for commercial products.
- Use Microsoft Word? Then might want to read this post about using track changes
- Paul Pehrson offers some advice for novice technical communicators
- While you shouldn’t need it, here’s a business case for tech writers to get access to development information
- Kai Weber looks at two words every lone writer should know: later and no
- Learn what a help authoring tool gives you over Drupal
If you missed them, take a read. If you read them, then read them again. You never know what you may have missed!
- Sprinting to a manual
- Larry Kunz answers the question Content strategy for technical communicators: what happens to my doc plan?
- Technical writing and journalism: yes, there are parallels
- Blurring the lines between the Web and the desktop
- Three simple and subtle ways to improve your writing
- Idealism and realism