[bmelton]

I got my initial exposure that way, but I had a hard time putting all the pieces together until I pulled Django out, and got a better understanding of which things came from where.

I should probably also point out that I'd only dealt with web languages before that point (PHP, ASP Classic, etc), so that's probably a negative point for me.

Everybody's different, for sure. For me, my Django suffered until I understood Python.

Can I ask what your pre-Django experience was? I wonder if there's any significance.

[dominicrodger]

Maybe previous experience is significant - I learned to program building websites (HTML -> early CMSes -> PHP), then did a computer science degree (mostly Java, though I did a bit of Ruby on Rails), then got a job in C++ (where I still work, 3 years later), which I'd been doing for a year or so by the time I picked up Django.

To be honest, I suspect my Python's not great - I probably ought to spend more time just writing Python - I'd hazard a guess that less than 20% of the time I spend building websites with Django is spent writing Python (most is probably spent fiddling around with HTML/JS). I can always get by - but every once in a while I learn something new that I wish I'd known about long before (I remember learning about list comprehensions at an intro to Python talk at Stack Overflow DevDays after I'd been using Python for about a year!).