Software Engineering KB

Home

❯

06 Development Process

❯

04 Code Quality

❯

01 Concept

❯

Documentation Practices

Documentation Practices

Feb 10, 20261 min read

  • code-quality
  • documentation

Documentation Practices

← Back to Technical Debt

README, API docs, architecture docs, runbooks. Good documentation reduces onboarding time, prevents knowledge silos, and enables self-service troubleshooting. Documentation should be treated as code — versioned, reviewed, and maintained.

Key Properties

  • README Standards
  • API Documentation
  • Runbooks

code-quality documentation


Graph View

  • Documentation Practices
  • Key Properties

Backlinks

  • Technical Debt

Created with Quartz v4.5.2 © 2026

  • GitHub