Bummer! This is just a preview. You need to be signed in with a Basic account to view the entire video.
Wrap Up0:51 with Kenneth Love
You've learned a huge amount about Django's class based views.
That's fitting since they're a huge change to how you've been writing views so far.
You don't have to use CBVs, but you'll find that they crop
up in a lot of other libraries and tools in the general community.
So you should at least be familiar with them.
For example, Django restaurant merch is built up around class based views.
Class based views can really help reduce the amount of code and
boilerplate you put into your projects.
Less code usually means fewer places for bugs to crop up, too.
You should also find that by using class based views, they're mix-ins and
building your own library of mix-ins, that you start being able to reuse more and
more of your code between features and even projects.
I've been a big fan of class based views since they came out.
They were actually the subject of my first ever conference talk.
So while I'm biased, I think they're an amazing part of Django and
one that everyone should use.
Thanks for learning with me, and I'll see you next time.
You need to sign up for Treehouse in order to download course files.Sign up