On Fri, Oct 7, 2011 at 10:47 AM, Chris Czub <chris.c...@gmail.com> wrote:
> Shawn -- what do you recommend instead? A friend and I recently had
> this debate. His suggestion was to split off as much behavior into
> smaller apps with only a handful of models in the models.py as
> possible, but I said that if it's not reusable, it shouldn't be an
> app. I still haven't found a solution for organizing large-scale
> Django app model structures that I'm happy with.
>
>
>
The statement that "if it's not reusable, it shouldn't be an app" is
patently incorrect.
Do what makes sense for your project because it gets the job done and it's
as easy as possible to maintain.
Any other rules of thumb are only helpful guidelines and shouldn't allow you
to go into "analysis paralysis" and not get any work done.
I wish I knew who said this first. Hopefully someone will reply to this
thread with the info:
A good programmer knows when to break the rules. A bad programmer
doesn't know he's breaking them.
It sounds like you know more than enough to do an excellent job, so go ahead
and do it.
--
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.
