As you may or may not know, I helped organize a two-day FLOSS Manuals book sprint at this year’s Toronto Open Source Week (held at Seneca College).
If you’re not familiar with a book sprint, read this for details.
This book sprint came about because:
- For the last two years, I’ve been promising Adam Hyde (head honcho of the FLOSS Manuals project) that I’d take a more active part in a book sprint
- I thought that this would be an interesting event to hold at Toronto Open Source Week
This time around, the goal was to complete a manual for the Mozilla Thunderbird email client. I hosted the book sprint in Toronto, and Adam Hyde took overall control from Berlin (where he lives).
It was an interesting two days, to say the least. Here’s a summary of what went down.
Below are the slides and notes for the presentation on FLOSS Manuals that Scott gave at FSOSS 2010. You can also find them on our page at Slideshare.
Jargon. Acronyms. They’re everywhere. Yes, even in technical communication.
Jargon and acronyms have helped bloat the English language and contributed to a level of obfuscation and confusion that’s deeper than an unknown foreign language. In fact, people who overuse jargon and acronyms often sound like they’re speaking a foreign tongue. Or just speaking in tongues …
As technical writers, we regularly run into this. I sure do. Worse, we can’t seem to escape jargon or acronyms.
But that doesn’t mean we have to put up with either. We can do a lot to minimize the amount of jargon and the number of acronyms in what we write. By doing so, we can make what they’re trying to convey clearer for any reader.
Tomorrow’s post comes from the keyboard of Larry Kunz. It’s an interesting complement to a recent guest post in this space.
Wondering what Larry has to say on this subject? Then drop by tomorrow to find out.