chef, 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
Getting Started with Django
11–20 of 75 posts
Re: Getting Started with Django
#12Why 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.
Even if you like this format better, the official-site tutorial is pretty good, and helpfully sets a common baseline for all Django learners (and all followup teaching). Having a 'canon' helps future steps, even if they diverge.
Re: Getting Started with Django
#13Why 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
#14How do you plan to fund the other lessons?
Re: Getting Started with Django
#15I'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
#16Wow, this looks really good. A decent django tutorial that covers all the ops side is somewhat lacking I feel, and this certainly looks pretty full. How do you plan to fund the other lessons?
Re: Getting Started with Django
#17I'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
#18chef, 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'm only confused at why installing pip/python isn't done via the chef file also. If you ever wanted to destroy the VM instance it'd be nice to not have to re-run any setup.
This tutorial doesn't require you to learn chef or use it directly in anyway so I don't think that's fair to include on the list of complaints.
Re: Getting Started with Django
#19chef, 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
It's nice for a tutorial to acknowledge this and give you a VM to play around with.
Re: Getting Started with Django
#20chef, 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
Because in the real world, you need to know things like chef, vagrant, ubuntu, apt-get, pip, virtualenv, heroku, ssh... if you want to do anything beyond building a demo app that only runs locally. I use all this stuff every day and I'm looking forward to going through this tutorial.
I'm also quite excited about the prebuilt VM that targets Heroku as my colleagues and I were just about to do this ourselves to retool our deploy process. This'll be an awesome start, thanks!