Office Pets. Part II: Blacky and Felix

This is the second (and last) part of our blog series about office pets. This time, we show off Blacky and Felix, two brothers. They are six years old, curious, and always hungry. more ...

Check if or check that? Or: Have you tried turning if off and on again?

How often do we read or write that we should check something? Example: "Check if the computer is connected to power." Clear message, no misunderstanding. But what if it says: "Check that the computer is connected to power." more ...

Ten questions for Ines Lasch, intern at parson

Ines Lasch just finished her vocational training as a technical writer and is doing an eight-week internship at parson. We asked her ten questions. more ...

Vocational Training for Technical Communicators. How Does it Work?

Anja Schiel, trainee, and Ulrike Parson, CEO of parson AG, offer their insights into the vocational training for technical communicators. more ...

Make Technical Documentation Intelligent - From Content Management to Content Delivery

In this article, Martin Kreutzer and Ulrike Parson describe how you fill content-delivery portals with intelligent information so that users quickly get the right answers to their questions. more ...

"Write the Docs" Impressions

On July 19 and 20, I joined the Berlin Unconference “Write the Docs”. I had not attended an event with open-space sessions and lighting talks before and did not know what to expect.

Turned out I was nearly the only one from Berlin. Also, few technical writers attended. Hardly anyone spoke German as most participants were from other European countries. All were in the software development business, among them many software engineers who specialize in writing software developer documentation. The discussions focussed on technical writing issues, but also on topics like “how to build a community”, “human testing of documentation”, or “smart documentation”. I found it exciting to see how differently tech writers and software engineers approach these topics. Sometimes software engineers try to reinvent the wheel because they are not familiar with the technical writing paradigms. But they make up for it: They are target-oriented and think outside the box.

Everyone was surprised when I told them about the largest European conference on technical documentation, the annual tekom conference.  During a lighting talk I spontaneously invited all of them to attend that conference and meet the technical writing community. In fact, I wish there was more exchange between tech writers and software engineers about developer documentation, API documentation, and documentation systems. Both sides could learn a great deal from each other.

I would love to attend a similar event again. But next time, I’ll take some tech writers along.

More information:

  • facebook
  • linkedin
  • xing