Also, because no one has mentioned it before: http://djangobook.com/
Django - starting from ground zero - any advice?
11–20 of 42 posts
Re: Django - starting from ground zero - any advice?
#12Don't worry when you start about doing them the best way. Its often better to make the mistakes (while still exploring) and your next app will just be that much better.
Good luck and great choice :)!
Re: Django - starting from ground zero - any advice?
#13Earlier quoted context omitted.
Good point; I think he meant "square one" instead of "ground zero" Oh... and when he's done he'll be on "cloud nine". English is weird.
All languages are weird, but pointing out a fairly substantial error is not a bad thing; unless it's done in a mean spirited way.
Re: Django - starting from ground zero - any advice?
#14I would also recommend "Python Pocket Reference" (3rd Edition) by O'Reilly. It really helped me get up to speed with Python in a short amount of time.
Good Luck.
Re: Django - starting from ground zero - any advice?
#15Then start coding. It's not too difficult. Some of the things with template engine are a bit funny, so try and not write any big code here, move it to the view/model. But otherwise remember that google is your friend.
My app is a geo based app, but I couldn't get geodjango to play nice. So I just installed the libs and went with that.
Re: Django - starting from ground zero - any advice?
#16Re: Django - starting from ground zero - any advice?
#17Also, if you want to keep up with the Django community and changes to Django code, I would recommend the "This Week in Django" podcast. Read more about it in Michael Triers blog at http://blog.michaeltrier.com/
Re: Django - starting from ground zero - any advice?
#18Re: Django - starting from ground zero - any advice?
#19Re: Django - starting from ground zero - any advice?
#20I like the post and the replies. Hacker News seems to be a really good forum for inquiries of this nature. But what on earth is "Damaged by Java" supposed to convey? I guess you find Python with Django to suit your particular needs better than Java, no reason to play down the latter though.
Java is good, but I always felt so constrained when writing code. It just felt like I had to write so much extra junk code like getters and setters that it made rapid prototyping which I do a lot a hassle.
Python was a breath of fresh air, and is a great language for hacking around in. Java is very useful and I still use it quite a bit.