Re: Django methodologies and best practices

On 18 oct, 06:55, Shakefu <shak...@gmail.com> wrote:
> So my questions are simple:
>
> What are your opinions on the best methodologies and practices for
> developing django apps and projects?
>
> What sort of planning do you do for an application or project?
>
> What development techniques do you use to help conceptualize an
> evolving project/app?
>
> For example:
> Do you prefer to write URLconfs first and let those guide your views
> which necessitate writing models, or write the models first and then
> views to perform operations on the models, or maybe even templates to
> help visualize what is needed for each section/page/app/whatever and
> then build backends to fulfill those needs...
>
> ... or any number of permutations along those themes.
>
> So what works for you? Why? What doesn't work or what stumbling blocks
> do certain routes present?

As far as I'm concerned - and given I have at least a rough functional
spec (but I fail to see how one could write any piece of software with
functional specs...) - models are of course the starting point. And
models that are not only dumb data-holders - most of the "operations"
on models should be handled by the models and managers themselves, not
by the views. Views are only an interface between the users and the
models, not a place to fill with business rules and 'low-level'
operations. FWIW, I don't even bother with views or urls before I have
a first working implementation of my models (remember you can test
your models from the interactive shell and/or python scripts).

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---