We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

The D is Silent: Challenges in Teaching Django

Formal Metadata

Title
The D is Silent: Challenges in Teaching Django
Title of Series
Part Number
40
Number of Parts
46
Author
Contributors
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
What are Django's important design decisions? Maximizes for the 90% case, but allows for uncommon cases Batteries included Emphasis on documentation and testing "Configuration over convention" and "Explicit is better than implicit" What are the benefits of each choice? Good high-level documentation Easy access to quality libraries An invitation to explore. What challenges are a consequence of these choices. Do I need all of Django? What is Django and what is Python? The mixed bag of "Configuration over convention" What does Flask do differently? How does Ruby on Rails differ and which parts are harder or easier to teach. Common mistakes when teaching Django How Django lends itself well to a Constructivist teaching approach, especially Jerome Bruner's "Spiral Curriculum".