Managing technical debt in (Django) Projects
summary
Concrete practices and tradeoffs decide whether watching is worth it: write tests when making assumptions, aim for quality over 100% coverage, and one homepage client test can give 80% discovery from a single test; use CI like Jenkins, Travis CI and tox and run postGIS tests, prefer code review and pair programming, add technical-debt notes in pull requests, bump requirements routinely, use Factory Boy and shell_plus for readable tests, avoid the Django test client for unit tests, and don’t customize the Django admin.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:58Understanding technical debt
- 3:41Testing strategies
- 7:32Managing software entropy
- 10:17Code quality and readability
- 13:34Code review and collaboration
- 19:16Team dynamics
- 21:28Organizational strategies
- 24:01Django-specific tips
- 27:16Development workflow
- 33:18Conclusion and resources
- 36:14Q&A session
related talks
28mTechnical Debt: Why it'll ruin your software
34mThe Technical Debt Trap
31mThis Old Pony: Working With Legacy Django Apps
53mDjango productivity tips and tricks
28mManaging Technical Debt at Scale
53mDjango productivity tips and tricks
21mBuilding maintainable Django projects: the difficult teenage years
24mStumbling Through Django and How Not To