Rethinking Software • 299 implied HN points • 25 Jul 25
- Good documentation should describe the current state of the software, not what it might be in the future. This keeps it relevant and useful.
- Documents like ADRs and RFCs can become roadblocks if they're written too early. They can hold teams back instead of helping them move forward.
- The best documentation comes from the code itself, such as generated docs or inline comments. This helps ensure that the documentation matches the actual software.