Technical writing panel (documentation edition)

[brunogirin]

There has been a fair amount of interest in the first technical writing panel and it generated a few tweets. This one from Jo Petty suggests that we should have more technical writers on the panel. This points to the fact that "technical writing" is an overloaded term and means at least the following two things:

• Writing articles and books for developers (the subject of the first panel)
• Writing product documentation, either for a technical or non-technical audience (what I think Jo does)

Assuming the first panel is a success, we could do another one focused on the latter, that could cover:

• Code documentation (what you put in the documentation comments),
• Technical libraries documentation and tutorials,
• User manuals for non-technical audiences.