prose like prose, code like code

Exit Survey
100%
In general, your argument in this post aligns with my experiences and perspective
Code review tools (e.g., Review Board) tend to exclude non-engineers from the content review process
Creating documentation isn't too different from the workflows in a creative writing workshops. In both cases, you write content and review with others, and then make updates based on the reviews. Write - review - update - repeat.
Gathering input and feedback from many different groups and perspectives is one of the most important techniques for creating good documentation
Reviewing only the parts of docs that have changed by looking at file diffs isn't as effective because it doesn't present the changes in the context of the whole
Overall, development processes for code and development processes for prose are significantly different
Comments/Suggestions:
Powered by QuestionPro Report Abuse
Create Your First Online Survey