- We’re not the only ones who think this: some people are crying out for good help
- Sarah Maddox discusses being part of a distributed team
- A manager’s guide to single sourcing
- Eddie VanArsdall takes an in-depth look at working with wikis — part 1 and part 2
- Twitter for usability testing and document testing? Anne Gentle explains how
- Here’s an idea: including recommendations in a user interface to enhance motivation
Yes, we succumbed to the siren song. Aaron’s been tweeting for a while, and Scott grudgingly did a Twitter experiment a while back. But a team Twitter feed? We figured why not give it a try …
But you can now follow us on Twitter here: http://twitter.com/dmnguys. We’ll be posting about tech comm, content, and related topics. While you shouldn’t expect us to be posting as frequently as Scott Abel, expect at least four or five tweets a day.
A few posts back, I wrote about some essentials for the consultant. Something that I deliberately left out of that post was a section about creating a Web site.
Whether or not a Web site is an essential is open for debate. I know a few freelancers and consultants who don’t have one and they’re doing well.
On the other hand, a Web site can increase your visibility. And it’s a great way for potential clients to view your work and learn more about you.
There are a number of ways that you can go about setting up your Web presence. Here are a few ideas.
At least as far as the tools of our particular trade go. I’ve mentioned it in this space before, and this is my solemn declaration of my position.
Gordon McLean summed it perfectly for me when he wrote:
The tool is not important
And Adam Hyde of FLOSS Manuals expanded on that thought when he told me that he’s found that there’s a lot of tool fetishism in the wacky world of technical communication. I’ve felt that for a number of years, but it took someone from outside of our wacky world to articulate that feeling for me.
I’m not going to go into a long rant about tool and technology fetishism. It’s been done before. Consult your favourite search engine to learn more.
This is coming from a guy who, a decade ago, thought it was FrameMaker or nothing. How times and opinions change … I realize now what I always seemed to know: how you write and publish content pales in importance to the quality of the content itself.
FrameMaker, RoboHelp, Word, OpenOffice.org Writer, Flare, Blaze, AuthorIt, DocBook, DITA, WebWorks. Single sourcing, content-based authoring, component content management. All of them (and many, many other tools, techniques, and technologies) have their uses, their strengths, and their places.
I’m not going to ponder which one is better than another, or which is the best. I’m not going to stress over radical changes to the interface in a new release of a particular app. I’m not going to swoon over the latest fad or fancy in authoring techniques.
Instead, I’m going to do one of the few things that I’m really good at: I’m going to adapt as needed. I’m going to take advantage of my knowledge and experience. I’m going to learn. I’m going to use the right tool and the right techniques for a particular job.
And that’s what works for me.
When I was in journalism school (and that was literally half a lifetime ago), the instructors constantly chivvied me and my classmates to write tight. That meant packing the most information into the least amount of space. It wasn’t easy, but when you did it, the result was like magic.
There’s a lesson there for technical communicators. I often compare tech writing with journalism. There are skills that bothjobs share, and the key to being effective is to keep what you’re writing short, to the point, and easy to read.
We’ll be returning to our regular blogging schedule next week. I hope …
- Here are a couple of reasons to use screenshots
- Ben Minson examines the difference between grammar and clarity
- This article presents some basics for the new user of XML
- Thinking about going freelance? This article looks at four things that you’ll miss from your day job
- An interesting article on XBRL and document management