On Wed, 2012-01-04 at 11:20 -0200, Andre Terra wrote: > I'm sorry, folks, but I'll have to vehemently disagree with a lot of > what has been said in this thread. To the OP, I'm sorry I didn't reply > any sooner. > > No, you don't need to go reading about what MVC means. Django is a MTV > framework, not MVC. There are similarities, but the differences are > enough to confuse your head if this is your first time with either > one. You should definitely stick to Django Book[1] for a definition on > what Models, Views and Templates are. Everyone who says otherwise is > wrong. Once you're comfortable with Django, feel free to explore other > frameworks so you can weigh the pros and cons yourself. > > No, you don't need to read the Python PEP on DB-API (?!?!). I'll go as > far as say you shouldn't. Not now and not for any time in the > foreseeable feature. You won't need to write raw SQL in Django until > you've reached a big bottleneck, and one that can't be solved in any > other way. Writing raw SQL is exactly what Django wants you to stop > doing. The ORM doesn't only exist in order to speed up development. It > provides a layer of abstraction that also allows for easy refactoring > and code improvement. SQL is not as flexible. > > The only PEP you need to read right away is PEP 8[2]. Learn it, love > it, memorize it, use it. Everything else will only bring marginal > benefits at such an early stage in the learning curve while also > carrying a level of complexity that will most likely be a hindrance to > your overall experience. > > Follow the tutorials and the django book (while outdated, most of it > should work fine). When asking questions, remember to paste a full > traceback and code examples. It might not make any sense to you, but > eventually you'll learn your way around it. #django on freenode is > rather helpful for quick questions and, if you know how to ask your > question[3], this mailing list will also prove useful. > > Finally, If you need some pointers on HTML/CSS/JS, start with the > HTML5 boilerplate[4] "framework". Everyone and their grandma seem to > be using it nowadays. It will give you enough of a starting point that > should make cross-browser compatibility as painless as possible, and > should get you going in a flash. > > I hope you find my advice convincing enough so that it may prevent you > from hurting your own learning process. I wish you only the best! > I fully agree - except for the caveat that reading up a bit on normal forms will not hurt. Django cannot design your db for you - you have to do it yourself. -- regards Kenneth Gonsalves
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
