Live data from Hacker News

Getting Started with Django

gettingstartedwithdjango.com

11–20 of 75 posts

Re: Getting Started with Django

#11
post #5

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

I don't see why giving the user more info on how to handle a full project since the beginning is a bad thing, the django part will certainly be independent of the rest of the tools.

Re: Getting Started with Django

#12

Why 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.

Why would you want this to duplicate material well-covered by the official-Django-site tutorial?

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

#14
Wow, 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

#16
post #14

Wow, 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?

The Kickstarter is funding all 10 originally planned episodes plus ~5 more covering FAQ-type situations.

Re: Getting Started with Django

#17
post #2

I'm very glad that you created this video series. It's going to be incredibly helpful for many developers. Keep up the good work!

This seems to be the perfect video to get setup before reading your book, which is very light on the "proper setup". I imagine that a book might not be the best format for that, or simply that this is not the content your main audience expect to start with.

Re: Getting Started with Django

#18
post #5

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

I actually think it's quite nice to supply a Vagrant VM (or at least the definition and cookbook) to get someone started quickly.

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

#19
post #5

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

One of the thing I usually find hardest about trying out any new web-stack is not necessarily writing the code but wrangling with all the ecosystem BS around it.

It's nice for a tutorial to acknowledge this and give you a VM to play around with.

Re: Getting Started with Django

#20
post #5

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

Perhaps a better title for the series would be "Getting Started with Django in the Real World"

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!

Post reply on HN