pragmatic-programmer
Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", "software craftsmanship", "technical debt prevention", "prototype vs tracer bullet", or "code ownership". Also trigger when evaluating build-vs-buy decisions, designing estimation approaches, or choosing between reversible and irreversible architectural decisions. Covers estimation, domain languages, and reversibility. For code-level quality, see clean-code. For refactoring techniques, see refactoring-patterns.
- Version
- 1.1.0
- License
- MIT
Pinned to revision 7a07e3df018f, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/pragmatic-programmer/SKILL.md
- skills/pragmatic-programmer/references/broken-windows.md
- skills/pragmatic-programmer/references/contracts-assertions.md
- skills/pragmatic-programmer/references/dry-orthogonality.md
- skills/pragmatic-programmer/references/estimation-portfolio.md
- skills/pragmatic-programmer/references/reversibility.md
- skills/pragmatic-programmer/references/tracer-bullets.md
Every link opens the file at its source, pinned to the revision this page describes.