11–20 of 34 posts
Neither Django Rest Framework nor AngularJS is actually used in this post..
Tangentially, I can't imagine using Django without DRF. It makes setting up RESTful(ish) APIs so easy. Even if you don't care much about the RESTful aspects, it provides a much nicer way to organize your code than default Django IMO. I especially like how serialization works versus Django forms.
It's shocking to me how something that should be so easy becomes so complicated. Why does the file structure need to be re-configured? What the heck are the __init__ files?? Virtual environments? I sort of know the answers but remain unsatisfied. And then the author sets up a needlessly overcomplicated data model situation.
Aww, what a tease. This is exactly what I'm diving into right now. Since part one was written in November, I'm guessing part three might show up around March? Anyone have any worthwhile Django learning resources to share? (Other than Django's own docs, which are great.)
Aww, what a tease. This is exactly what I'm diving into right now. Since part one was written in November, I'm guessing part three might show up around March? Anyone have any worthwhile Django learning resources to share? (Other than Django's own docs, which are great.)
There's a book called Django by Example by Antonio Mele that I think is pretty good. People love Two Scoops of Django as well. The former consists of a series of tutorials and the latter explains best practices to consider when writing Django apps.
1. Versions -- a lot of printed materials are just old by the time they come out.
2. None of them talk about large-scale projects, only smaller-scale personal blogs etc. as a first project. Or, put another way, many of the resources I find target beginners instead of intermediate/advanced learners.
Neither Django Rest Framework nor AngularJS is actually used in this post..
This reminds me of the kickstarter to build django tutorials. Lots of talks and finally halting halfway ... That's the difference between Django and Rails (and now Node). Ressources are scarce and unreliable ...
It's shocking to me how something that should be so easy becomes so complicated. Why does the file structure need to be re-configured? What the heck are the __init__ files?? Virtual environments? I sort of know the answers but remain unsatisfied. And then the author sets up a needlessly overcomplicated data model situation.
I use DRF with Angular at work, so I'm interested in seeing where this series goes. Tangentially, I can't imagine using Django without DRF. It makes setting up RESTful(ish) APIs so easy. Even if you don't care much about the RESTful aspects, it provides a much nicer way to organize your code than default Django IMO. I especially like how serialization works versus Django forms.
Aww, what a tease. This is exactly what I'm diving into right now. Since part one was written in November, I'm guessing part three might show up around March? Anyone have any worthwhile Django learning resources to share? (Other than Django's own docs, which are great.)
There's a book called Django by Example by Antonio Mele that I think is pretty good. People love Two Scoops of Django as well. The former consists of a series of tutorials and the latter explains best practices to consider when writing Django apps.
I've found books by Packt Pub to be of variable quality, and DbE does have some typoes/errors, but the content so far has been quite good.