IMO, CBVs are good, but for many cases FBV are simpler to code and easier to understand.
Django's FBV's are far from perfect and I think they really could benefit from some small changes to the way things are done, but I agree with the above links that CBV's were a step in the wrong direction.
It's one more line, and is much more explicit in what it handles.
I've come to a snag at "Writing a Test" (http://effectivedjango.com/tutorial/models.html#writing-a-te... ) though, it's not clear which file I should be adding the test class to.
From following the tutorial I would think models.py but from browsing the file structure I would expect test.py
Btw, there are some weird formatting issues in the tutorial (underscores after links?).
Similarly, ways to mimic single-page-app URLs from the server side, for first-load speed or SEO benefits, could be discussed.
Perhaps there's a more narrow 'scope' defined for this project, but simply from the title, it seems an 'effective' Django developer would appreciate guidance for the best ways to do AJAXy things (including, especially, RESTy web services for backing AJAXy front-ends).
There is also an is_ajax() test in Django (not that useful) and various apps that provide REST interfaces that you'd probably want to use for bigger AJAX-y apps.
It seems to me the only durable advantage to the free version is that if it isn't working out you can abandon it after 15 minutes at a fraction of the cost. If there were a credible way to sell knowledge products "satisfaction guaranteed" I'd think that people would be a lot less sensitive to the difference between free and $14.