A great strength of Django is how much functionality there is baked in without the developer doing anything to obtain it.
A corollary of this is that there’s a great deal of functionality in Django which the average developer is hardly aware exists. The happy dev is pleased to ignore the problems that have been solved for them as their requests rush in and their responses rush out.
There's Middleware, Signals, Authentication, Caching, Internationalization, Serialization and ... a lot more and that's just the core framework.
In this talk we’re going to stop and admire the view .
We’ll demonstrate the effects that these core aspects of Django have on a request - response cycle by reviewing how they work and feeling the pain of what life would be like without them.
My talk is aimed at the average Django dev who has been happy to ignore what goes on under the hood. By better understanding the machinery that Django relies on it gives us all the opportunity to exploit it in our work and, of course, to impress our colleagues !
Richard is a Wellington, New Zealand, based freelance developer. He's been working with Python for twelve years and Django for three.
He works for a variety of Kiwi and Aussie clients providing business solutions and offers a discount to those who let him use Python.
In recent times he's taken to consorting with Node but that's probably just a mid life crisis.
An old school RDBMS developer, before he started work on Django he thought an Orm was a type of wading bird and when he found out the truth he wasn't sure he liked it. Since then he's taken to it like a duck to water and now spends his evenings paddling around django.contrib making squawking noises.
