[mbil]

Cool app. I agree with your points about Confluence's issues.

> At this point documentation becomes viewed as a time sink and people start to prefer other practices like pairing, comprehensive user stories and tests. These unfortunately are only a bandaid solution to the problem...

I think that "pairing, comprehensive user stories, and tests" are all good things you should have anyway, and documentation can't be a replacement for them.

[missingrib]

Can someone explain what "pairing, comprehensive user stories, and tests" are? Are these actual terms or is the author just talking about teammates getting together to work on an issue?

[v64]

I assume they mean pair programming [1], user stories which are used in agile methodologies [2], and test-driven development [3].

[1] https://en.wikipedia.org/wiki/Pair_programming

[2] https://en.wikipedia.org/wiki/User_story

[3] https://en.wikipedia.org/wiki/Test-driven_development

[mahomedalid]

I interpret that as:

Pairing - Pair programming, which if one of the developers has experience with the product will solve questions that you otherwise will solve with docs.

Comprehensive User Stories - User story like in Agile/Scrum, where it has an acceptance criteria, goals, description, etc. and can be used to track back documentation of features.

Tests - User test cases, which can be a replacement of the documentation of how to use the product or the intent of the features.

[francescol]

Sorry, that could have been clearer. I meant the practice of pair programming, including user stories in Jira tickets (to explain why the ticket exists in the first place) and tests for your codebase to help others understand how the code operates.

[francescol]

Thanks! I completely agree with you, will edit to make that more clear