Hey Cal, Firstly, I will not keep a blog up to date. But rest assured I will find my way to contribute back to the community. Secondly, I want to say thanks for taking the time to share your thoughts and experience.
I never stop learning new things and this is a great opportunity for me to get acquainted with new communities and tools. I am quite bored if there is no challenge, so I decided to start a business powered by recent and awesome technologies that I don't master yet. I would be less enthusiastic about it if I had to use Java or PHP. This applies to everybody here, I'd like to thank you all for contributing and helping new comers like me. Thanks for pointing me to the right direction. Now if you'll excuse me, I've got some serious code to write! Thanks again. On Monday, March 25, 2013 3:28:51 PM UTC+1, Cal Leeming [Simplicity Media Ltd] wrote: > > Hi Benjamin, > > Some others have already made some good suggestions, so I'll throw some > general comments in. > > Tim made a good suggestion of 2scoops, you could also try; > http://learnpythonthehardway.org/book/ > http://www.djangobook.com/en/2.0/index.html > > In my own personal opinion, I think you would benefit hugely by starting > out with some of the URLs mentioned above and in this thread, as well as > these; > > http://eddychan.com/post/15775730174/how-i-learnt-enough-python-django-to-be-dangerous-in-1 > http://tech.yipit.com/2012/02/28/learn-django/ > > There is also 'Django by Example', although it sadly does not use Class > Based Views; > http://lightbird.net/dbe/ > > There is also a lot of projects that use Django which have been open > sourced on Github; > https://github.com/search?q=django&ref=commandbar > > Frankline/Shawn comments of "just dive in" is spot on, and Tomas comment > of "you need to learn" is also correct. The key thing is having a balance > of the two, programming will always and forever be a learning curve, and > the day you stop learning is the day you should find a different job. I > look back on code that I wrote 2-3 years ago and think to myself "this is > atrociously bad", and I will probably think the same again in another 3 > years time! I have 7+ years of Python and 3+ years of Django experience, > yet I often take huge amounts of time out to re-train myself on specific > areas (where cash flow and spare time will allow). > > The point is you have to decide where to draw the line on your own > knowledge, and that is entirely dependent on your end goal. For example, if > you want to build a small website with technical requirements that are not > out of the ordinary, then you probably don't need to learn all the depths > of how different databases work, and instead focus on learning how to > construct clean/style conforming code. However if you were building > something that has never ever been done before, then you might prototype it > in a single Python script and tidy it up later, so you can quickly adapt. > > Hope this helps a little bit! > > Cal > > > On Mon, Mar 25, 2013 at 11:17 AM, Benjamin Marsili < > benjamin.an...@gmail.com <javascript:>> wrote: > >> Hey everyone, >> >> I am trying to design a website from scratch using django, it's my first >> time using it and I read the basic tutorials. Now it's time to get things >> done and I wonder where to begin. I don't want to make design mistakes. >> >> Let's take an internet website for example. There would be a planning and >> user accounts (at least). >> >> 1) Should I create 2 apps, one for user accounts and one for the >> planning? If yes, the rest of the code (templates, login page and other >> basic pages) should go in the project and not in an app? >> >> 2) Should I start by creating templates for the look of the website? Or >> should I populate and test the DB models first? >> >> 3) Where would the generic code go? For example if I want to share a >> function that will return the HTML header, do I have to copy it in each app? >> >> If you have guidelines to get a project going around django please share >> them here! >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-users...@googlegroups.com <javascript:>. >> To post to this group, send email to django...@googlegroups.com<javascript:> >> . >> Visit this group at http://groups.google.com/group/django-users?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
