this repo has no description
📝 Add insight on documentation value in capturing design decisions
+1
+1
Documentation.md
+1
Documentation.md
···
34
34
- Ask the "So what" question to every sentence that you write.
35
35
- Prefer active voice to passive.
36
36
- Most docs are short-lived and used for point-in-time discussions. However, some documents serve for a longer time. To have your writing stand the test of time, avoid using references that change with time or location.
37
+
- Documentation valuable if it captures the design decision and intention at the time of the creation of the software, rather than the functionality of the software itself.
37
38
38
39
## Resources
39
40