These past weeks I have gone back to my Django resources to try to learn the last stages of the Django modules, business logic, etc.
I most say that I have actually skip most of the documentation and gone into more trusty tutorials that do one task, and learn from it.
One of the tutorials I found was for the CRUD system, something basic enough to grasp it easily. However, even then it wasn’t as easy as I thought.
The writer develop an internal debate between a Class based view, and a Function based views. As you know, Views is where the business logic of the applications are. So even if this learning was good and simple, I might need to multiply it by 2. Not that is necesarily bad, but still, wish it was simple.
I went to a DjangoCon videoset on youtube. One of those was about teaching Django at University, and there was a very interesting explanation on how Django sometimes is unecesarily complicated. Also some recomendations like the Django Girls group, and a book called Two Scoops of Django, something that I already had on my resources.
This gave me some idea into their philosophy. Hearing someone recognizing that the documentation is not always the best way for learners to understand whats going on. Building on top of an understandment is something that is helpful for learners build their best interpretations.
Telling a n00b to study this documentation with everything you will ever needed inside doesnt mean he would actually go through it all. On other words, most people will rather create a fix for their inmediate need.
At the moment some of these needs are:
– Creating a cookbook
– Creating mentoring mechanisms
– Generating 50 shot view of whats going on