Getting Started with Django
gettingstartedwithdjango.com
Getting Started with Django
1–10 of 75 posts
Re: Getting Started with Django
#2I'm very glad that you created this video series. It's going to be incredibly helpful for many developers. Keep up the good work!
Re: Getting Started with Django
#3a minor nit: fix the spelling in the header "Getting to Heorku"
Re: Getting Started with Django
#4a minor nit: fix the spelling in the header "Getting to Heorku"
done
Re: Getting Started with Django
#5chef, vagrant, ubuntu, apt-get, pip, virtualenv, heroku, ssh.. oh there it is, sth about learning django. I'm saying it not to diss your work, but don't you think setting up a linux env on a vm and signing up to heroku shouldn't be the point of a django tutorial? point explained in another discussion about zed's approach to writing 'learn x the hard way' https://news.ycombinator.com/item?id=4961593
Re: Getting Started with Django
#6Why do I need to go through the Django tutorial before starting "Getting Started with Django"? I thought this would be my first stop, not something after the official Polls app.
Re: Getting Started with Django
#7chef, vagrant, ubuntu, apt-get, pip, virtualenv, heroku, ssh.. oh there it is, sth about learning django. I'm saying it not to diss your work, but don't you think setting up a linux env on a vm and signing up to heroku shouldn't be the point of a django tutorial? point explained in another discussion about zed's approach to writing 'learn x the hard way' https://news.ycombinator.com/item?id=4961593
I actually think setting up those tools in the tutorial video is great. It's nice to see how a real django dev builds a production app. This stuff is rarely covered in other more simplified tutorials.
Re: Getting Started with Django
#8While others are complaining about all the up front set up; this is actually something I like. Base tutorials always seem to be missing that 'something' that takes what you've learned and turns it into a real world application.
Even if its not step one, I would prefer more tutorials to have a full fledged 'Getting Set Up' section; even if it becomes arbitrary. It makes sure everyone can get on the same page no matter where they come from.
Re: Getting Started with Django
#9I'm looking for a good Django tutorial that includes examples of developing with BDD and TDD. The way I learned Rails included RSpec and Cucumber, and that made a huge difference.
Re: Getting Started with Django
#10chef, vagrant, ubuntu, apt-get, pip, virtualenv, heroku, ssh.. oh there it is, sth about learning django. I'm saying it not to diss your work, but don't you think setting up a linux env on a vm and signing up to heroku shouldn't be the point of a django tutorial? point explained in another discussion about zed's approach to writing 'learn x the hard way' https://news.ycombinator.com/item?id=4961593
"3. Make it work for Windows, OSX, and Linux if you can."
This is the reason the VM was introduced. So that no matter what OS the user is running, they can follow along without having to go search for ways to get all this setup and running. The setup is very minimal thanks to Chef and Vagrant.
Kenneth is trying to teach best practices and tools to use. He also explained in the beginning of the video that you should be comfortable with a terminal and text editor that you like. This shouldn't be your first time looking at a terminal.
Heroku is a simple way to get your project out to the public and it's free. Nothing inspired me more as a developer than having others look at my work. I think it adds a little bit of excitement to be able to show your work to others almost immediately. Even if it's something small, it's still something to "show off" and feel good about.