> Markdown version of [/videos/925-i-will-remember-that-and-other-lies-why-documentation-matters-and-it-makes-your-apps-better?t=1472](https://www.wearedevelopers.com/videos/925-i-will-remember-that-and-other-lies-why-documentation-matters-and-it-makes-your-apps-better?t=1472). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# "I will remember that" and other lies - Why documentation matters and it makes your apps better

Think you will remember why you wrote that complex workaround six months from now? Stop lying to yourself and discover how proper documentation actually builds better apps.

- **Speakers:** [Luise Freese](https://www.wearedevelopers.com/@luise-freese)
- **Event:** World Congress 2024
- **Published:** August 13, 2024
- **Duration:** 25:25
- **URL:** https://www.wearedevelopers.com/videos/925-i-will-remember-that-and-other-lies-why-documentation-matters-and-it-makes-your-apps-better

## Summary

Addressing the ingrained 

**Keywords:** dummy

## Chapters

1. **Defining types of product documentation for software projects** (03:40) — Product documentation encompasses essential requirements, design records, API references, and test strategies rather than just basic project readmes.
1. **Establishing clear specifications and software design descriptions** (05:53) — Writing comprehensive technical requirements and concurrent design documents establishes a single source of truth that prevents costly misunderstandings.
1. **Writing source code comments and release notes effectively** (08:27) — Descriptive in-line comments and automated release notes provide crucial context for maintaining codebases over time.
1. **Incorporating expected user experience and accessibility guidelines** (10:44) — Documenting user personas, story maps, and accessibility guides ensures holistic product design from initial requirements to ongoing evolution.
1. **Driving business objectives through comprehensive technical documentation** (12:57) — Centralizing project information mitigates development risks, accelerates developer onboarding, and prevents teams from repeating historical mistakes.
1. **Improving software architecture skills through consistent writing habits** (19:01) — Detailing software functionality deepens fundamental architectural understanding, strictly supports legal compliance, and inherently leads to cleaner implementations.
1. **Establishing ongoing documentation habits during software development** (24:32) — Logging architectural decisions concurrently alongside development workflows captures crucial context before it is irrevocably forgotten.

## Related Moments

- [Designing technical documentation for cross-functional audiences](https://www.wearedevelopers.com/videos/379-communicate-efficiently-with-software-architecture-diagrams) (from "Communicate efficiently with Software Architecture Diagrams")
- [Identifying common types of technical documentation](https://www.wearedevelopers.com/videos/681-technical-documentation-how-can-i-write-them-better-and-why-should-i-care) (from "Technical Documentation - How Can I Write Them Better and Why Should I Care?")
- [Boosting team productivity with comprehensive engineering documentation](https://www.wearedevelopers.com/videos/927-documentation-as-a-tool-introducing-documentation-driven-development) (from "Documentation as a Tool: Introducing Documentation Driven Development")
- [Discovering the long-term value of continuous software code documentation](https://www.wearedevelopers.com/videos/798-continuous-documentation-for-your-code) (from "Continuous Documentation for Your Code")
- [Using understanding-oriented documentation to explain integrations and software architecture](https://www.wearedevelopers.com/videos/798-continuous-documentation-for-your-code) (from "Continuous Documentation for Your Code")
- [Introduction to documenting architecture decisions in agile teams](https://www.wearedevelopers.com/videos/48-work-efficiently-with-architecture-decision-records-adrs) (from "Work efficiently with Architecture Decision Records (ADRs)")

## Related Articles

- [The real reason we document our code](https://www.wearedevelopers.com/magazine/518-the-real-reason-we-document-our-code)
- [Humanizing Your Documentation](https://www.wearedevelopers.com/magazine/133-humanizing-your-documentation)
- [7 Best Steps For Writing Good Software Technical Documentation](https://www.wearedevelopers.com/magazine/113-7-best-steps-for-writing-good-software-technical-documentation)
- [Technical Documentation For Developers](https://www.wearedevelopers.com/magazine/128-technical-documentation-for-developers)

## Related Jobs

- [Lead Software Engineer (f/m/d)](https://www.wearedevelopers.com/jobs/48296-lead-software-engineer-f-m-d) at **Personio SE & Co. KG**
- [Product Owner - Artificial Intelligence](https://www.wearedevelopers.com/jobs/ext/396346-product-owner-artificial-intelligence) at **ZEISS Group**
- [Manager, Technical Support](https://www.wearedevelopers.com/jobs/ext/737543-manager-technical-support) at **Twilio**
- [Head of AI Applications](https://www.wearedevelopers.com/jobs/ext/1231536-head-of-ai-applications) at **ZEISS Group**
- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Enterprise Architect - ERP](https://www.wearedevelopers.com/jobs/ext/1965168-enterprise-architect-erp) at **ZEISS Group**