4 ms·
I just completed reading it. I haven't been working with django recently and having completely read the book, I am now up to date. * The book has a lot of pra
by scorpion032 14y ago
I just completed reading it.
I haven't been working with django recently and having completely read the book, I am now up to date.
* The book has a lot of practical advice having developed using django for years. For example, the book recommends, whenever you have a custom manager, always explicitly define `objects` as the default manager, before the custom manager.
* The book makes a recommendation; but also mentions alternatives where applicable. The authors prefer a 3 tier project layout but also suggest that a lot of people prefer the 2 tier layout where the `manage.py` is in the root of the repository. Similarly in the chapter on the Class Based Views. The book suggests an approach and also includes other ones.
* Includes the latest and the new changes in the django 1.5 wrt the User model and how to inherit.
* Recommends and suggests many good third party applications. More books need to do this.
* Provides good review material (if you already know) about Security, Deployment, performance etc.
All of this, just over the top of my head.
Real world advice is often hard to come by. Whether you are a professional or a novice or just checking out django, you should buy this book.
- deservingend 14y agoIf this is off the top of your head, why post the exact same thing to reddit?
- nodata 14y agoYour comment makes no sense. He had some thoughts and posted them. It doesn't matter where he posted them.
- scorpion032 14y agoI posted it on reddit first off the top of my head directly. Then I noticed the thread on Hacker News and started writing a comment; deleted it and copy-pasted from my own reddit comment and went to bed peacefully. Which part of this is not right?