3 ms·
I do wholeheartedly agree about user guides. But I'll rephrase the statement as "Your documentation team should write a user guide". If your big enough to need
by intrasight 6y ago
I do wholeheartedly agree about user guides. But I'll rephrase the statement as "Your documentation team should write a user guide". If your big enough to need a user guide, you're big enough to have a documentation team. That can be a team of one for starters. Comparative advantage. Programmers should program.
- deleted 6y ago[deleted]
- MattGaiser 6y agoI don't think you read the article. "User guide" is not what you think it is in this context.
- intrasight 6y agoIn addition, I'll say that your documentation team should use real technical writing software like FrameMaker and not some lame ascii markup thingy like Markdown, RST, etc. Programmer written documentation should be embedded in their code. Just joking. Do whatever you want - it's a free country (mostly).