Reusable Apps
summary
Argues that reusable Django apps win by being small and focused: do one thing and split features into separate apps (example: a simple user registration app plus a separate Django profiles app and a contact form), design flexible APIs (allow pluggable form classes, template_name and success_url, use reverse lookups and get_model, push logic into managers and registries), avoid project coupling and package with setuptools / easy_install, and cites ecosystem scale (hundreds of projects on Google Code, 1,636 listed sites) as proof it works.
AI-written summary · about
chapters (35)
- 0:00Intro
- 1:06The fourfold path
- 3:24Keep a tight focus
- 4:33Warning signs
- 6:50User registration
- 9:39django-profiles
- 10:41The monolith mindset
- 11:29The Django mindset
- 11:57Django encourages this
- 12:40Should this be its own application?
- 13:13Unrelated features
- 14:51Orthogonality
- 15:29Reuse
- 16:14I wanted a blog
- 18:28Common sense
- 19:59Form processing
- 21:31URL best practices
- 22:34Working with models
- 24:34Learn to love managers
- 25:45Advanced techniques
- 29:06Bad API design
- 31:39So you did the tutorial
- 32:07Why (some) projects suck
- 32:29A good "project"
- 32:44Advantages
- 33:40What reusable apps look like
- 34:35General best practices
- 36:35Templates are hard
- 37:20Either way
- 38:24Documentation-driven development
- 39:12Django will help you
- 40:16Recap
- 41:13PyCon 2007...
- 41:40DjangoCon 2008
- 43:03Good examples
related talks
19mPatterns for Extensibility
26mDjango Unstrained
33mThe D is Silent: Challenges in Teaching Django
28mFunctional Web Apps: A New Paradigm For Web Development
23mIntegrating Web Apps
24mIs Django too Complicated
49mScalable Best Practices for Your Development Team
29mHow Django helped us make a better conference website