Lessons Learned in a Large Django Project
summary
A large Django project rebuilt the Guía Repsol site with 80,000 tourist entries and 500 articles, delivered an initial version in 18 months and a six-month handover. The stack used Django, Django CMS and a custom API exposed to mobile, migrated data from SQL Server to PostgreSQL via a custom ETL, added map-provider adapters and a clustering system for many map points, and found insufficient tests caused fear of changing code—leading to the practical recommendation to separate the API and the front end from the start.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:29PREPARE FOR CHANGE, BUT DON'T MAKE IT UNNECESSARILY COMPLICATED
- 8:59KNOW THE "GUTS" OF YOUR TECHNOLOGY AND DARE TO DEVELOP SOMETHING YOURSELF
- 10:45USE A DISTRIBUTED VERSION CONTROL SYSTEM
- 12:35DOCUMENTATION-DRIVEN DEVELOPMENT
- 13:55CONTRIBUTE TO FREE SOFTWARE AS MUCH AS YOU CAN
related talks
26mDjango at
16mBrazil: How we are gaining space with Django
21mBuilding maintainable Django projects: the difficult teenage years
28mThe promised Django Land; the tale of one team’s epic journey...
23mThree Django Apps in a Trenchcoat: Writing an event management website with not a lot of time
54mDjangoCon 2008 Panel: Django in Journalism
29mHow Django helped us make a better conference website
33mHow I learned Django while working at Eventbrite