Stumbling Through Django and How Not To
summary
Begins with concrete fixes: create per-project rooms using virtualenv and virtualenvwrapper so dependencies never collide; save CSS/JS locally so offline dev doesn’t break the UI (no more missing velociraptor); use feature branches — e.g. git checkout -b oh_my_god_what_have_I_done — to make a safe panic button; keep secrets out of repo by exporting SECRET_KEY and API keys as environment variables in the virtualenv activate script; community study groups solve baffling bugs fast and repeatedly restore working builds.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:59Throwing House Parties without Causing Anaphylaxis
- 2:32Why the deuce do I need virtual environments anyway?
- 2:44Brace yourself for analogy impact.
- 6:52virtualenvwrapper Super Duper Extra Lazy/Not Lazy Version
- 8:19Saying "No" to Seamonsters and "Yes" to Pregnant Daddy Seahorses
- 8:39I'm gonna make a web app!
- 11:29Protecting Your Velociraptors (with Django)
- 14:26Terrified Abandonment of Dreadful Mistakes
- 17:23If you're going to make changes, make a new branch.
- 17:34Being Suave and Mysterious (with Django)
- 19:23Virtual environments to the rescue!
related talks
53mDjango productivity tips and tricks
53mDjango productivity tips and tricks
21mBuilding maintainable Django projects: the difficult teenage years
33mHow I learned Django while working at Eventbrite
01h 06mEffective Django
31mThis Old Pony: Working With Legacy Django Apps
33mThe D is Silent: Challenges in Teaching Django
42mManaging technical debt in (Django) Projects