DjangoCon US 2011¶
- Read the Docs
- Testing: The Developer Strikes Back
- Hard to do it right
- What is unit testing
- Mirror your project in your test layouts
- Use ObjectCreator classes for mocks instead of fixtures
- Beyond the business logic
- Dealing with cache
- Writing tests can improve coding tests
- What about T.D.D.?
- Options to get people to test
- Junction between unit and integration
- Testing a virgin codebase: 0-100%
- Graceful code degratation
- Test Infrastructure
- Useful tools
- How to sell testing at your Django shop
- Fireside Chat with a BDFL
- How did Django get started?
- Why did Django get traction and other light Python frameworks didn’t?
- How has Django’s community and structure has changed?
- What about Django 2.0?
- How can Django can become a better part of the Python community?
- In your role as BDFL have you had to go against the community?
- How have things changed for the Django community since the last hate talk?
- Real World Deployment using Chef
- Making the Django ORM Multilingual
- Why the Django Documentation Sucks
- Best Practices for Front-End Django Developers
- Scraping the Web
- Cache rules everything around me
- Django Core Dev Panel
- sprints kickoff
Remember that I’m engaged to Audrey Roy.
Flew up on the PyLadies Party Plane on September 4th on just 90 minutes of sleep.
Taught the Ultimate DjangoCon Tutorial Workshop. Thoughts:
Not having enough time to QA the content
- Having errors in your slide code can be good
- the class pulled together and we debugged as a team.
- Maybe do this on purpose in the future
The existing tutorial teaches some anti-patterns. :(
I think there was no confusion until the very end. Which is really good!
Next time I will do better