Code Writing and Design
summary
About 6,000 ticket reviews reveal recurring mistakes and the fixes that actually stick: always include a minimal failing test (tests take 35–60 minutes locally), submit an SVN diff (use svn add for new files), follow pep8 and the docs/contributing guide, and consider all supported backends (MySQL, sqlite, PostgreSQL, Oracle, Windows edge cases). Real bugs include pickling protocol mismatches (protocol 0 vs 2), len swallowing exceptions, and an infinite-memory loop from objects with __getitem__ but no __len__; the accepted fix raises a clear error rather than adding 14 methods.
AI-written summary · about
chapters (5)
- 0:00Start
- 13:19Code Quality
- 15:27Comments
- 27:04The Wisdom of Crowds
- 33:34Django Runs on Multiple Operating Systems
related talks
42mManaging technical debt in (Django) Projects
26mow to Enjoy Debugging in Production with Karen Tracey
10mYour Web Framework Needs You: An Update
27mJane Austen on PEP8...
50mLightning Talks III
31mThis Old Pony: Working With Legacy Django Apps
24mStumbling Through Django and How Not To
21mBuilding maintainable Django projects: the difficult teenage years