Max is a life enhancer for tech & entrepreneurship. Which seeks to blend both to build innovative products or services for the world that solves hard problems.
It's really comprehensive and easy to read, it's much better when I was starting out as it took me a while to understand Django using 2 Scoops of Django and Coding For Entrepreneurs to help me to land an internship 2 years+ back.
I believe the hardest part to understand Django is the difference between MVC and Django's MVT model.
Plus the differences between class-based view or function-based view on when is a great time to use it.
Lastly, With the release of Django 3. I believe it will become more relevant especially the part where ASGI is actually supported by Django 3.0 onwards.
Former product manager turned data engineer with ongoing identity crisis. Breaks everything before learning concepts known as ‘best practices’. Completely normal and emotionally stable.
Thanks Max, that means a lot! I completely agree with your top two pain points for learning Django.
MVC was a foreign concept to me until I picked up Django. Learning an entirely new software design pattern in parallel to a monolithic framework such as Django is a VERY tall order (in retrospect, I'm not sure how I even managed to stick through it). There may very well be an effective way to convey these concepts to aspiring devs, but I'm not quite sure I've nailed down what that method would look like. It's something I'd love to tackle.
Confusion behind class-based vs function-based views actually threw me for a ride just the other day! This aspect of Django is in need of clearer documentation... perhaps a great candidate for the next post!
Thanks again for chiming in! It's reassuring to hear my personal pain points are shared with others... it's a great way to know what to write about next :)
Max is a life enhancer for tech & entrepreneurship. Which seeks to blend both to build innovative products or services for the world that solves hard problems.
It's really comprehensive and easy to read, it's much better when I was starting out as it took me a while to understand Django using 2 Scoops of Django and Coding For Entrepreneurs to help me to land an internship 2 years+ back.
I believe the hardest part to understand Django is the difference between MVC and Django's MVT model.
Plus the differences between class-based view or function-based view on when is a great time to use it.
Lastly, With the release of Django 3. I believe it will become more relevant especially the part where ASGI is actually supported by Django 3.0 onwards.
Thanks Max, that means a lot! I completely agree with your top two pain points for learning Django.
MVC was a foreign concept to me until I picked up Django. Learning an entirely new software design pattern in parallel to a monolithic framework such as Django is a VERY tall order (in retrospect, I'm not sure how I even managed to stick through it). There may very well be an effective way to convey these concepts to aspiring devs, but I'm not quite sure I've nailed down what that method would look like. It's something I'd love to tackle.
Confusion behind class-based vs function-based views actually threw me for a ride just the other day! This aspect of Django is in need of clearer documentation... perhaps a great candidate for the next post!
Thanks again for chiming in! It's reassuring to hear my personal pain points are shared with others... it's a great way to know what to write about next :)
Hahaha I should thank you as well.
Since I was thinking of what are the other topics for me to write for Django.
If it is such a major pain point.
I might write it down and play around with the newly released Django 3 on how is done.