- Writing your resume? Then maybe you should think like a tech writer
- Some advice on how to justify hiring technical writers in tough times
- Great designs should be experienced and not seen
- Do you know the difference between usability and thinkability?
- Tom Johnson talks about Malcolm Gladwell’s Outliers and why you’re a successful writer
- Some thoughts about using nouns as verbs in UIs
Yesterday, Scott Abel posted that PubsNet (the company behind the DocTrain conference series) was closing up shop and that DocTrain was no more. Let’s just say that this was a bit of a surprise, and it really saddened me. Sure, it’s a sign of the current economic times but that doesn’t make it any easier.
If you’ve been reading this space for any length of time, you know that over the last few years Aaron and I have been fairly regular participants at DocTrain. We’ve spoken together at DocTrain West twice, participated in a panel another time, and I presented solo at DocTrain East last year. DocTrain was good to us while it lasted.
Toronto Wiki Tuesdays is back, tomorrow (May 19th) in fact. This time around Michiel Duvekot, Global Technical Lead for Maya Product Support at AutoDesk, will be presenting. His talk will be on how AutoDesk uses semantic wikis to capture knowledge for customer support.
If you’re a wiki enthusiast in the Toronto area, or just want to learn about how one firm is using wikis to capture knowledge, then this is definitely a great way to spend a couple of hours on a Tuesday evening. If you want to attend, you’ll have to join the Toronto Wiki Tuesdays group at Meetup.com.
Unfortunately, I won’t be able to attend. The universe has once again pointed the you-know-what-with-me gun in my direction and my Tuesdays are filled until August.
Then, we’ve got some good news for you. We’ve installed a WordPress plugin that doesn’t truncate longer posts — the ones that we split with Read the rest of this entry links — when viewed in a reader (like Google Reader).
Thanks to Ben Minson for getting us off our sorry posteriors and finally doing something about this.
What’s interesting about the book isn’t its subject matter, but rather the way in which it was written. Believe it or not, the book was done in PowerPoint. Yes, PowerPoint. A piece of software that’s generally used to create presentation slides.
Shortly after the book’s release, Tim O’Reilly recently blogged about the book, the writing process, and how the approach to the The Twitter Book was an attempt to reinvent the concept of the book in the age of the Web. Read O’Reilly’s post for the details.