[grasshoper]

With Django, I've learned to avoid anything that tries to do too much. Small apps or collections of code that aim to solve very specific problems seem to work with the least hassle. With a carefully defined and limited scope, these apps have a much easier time integrating into existing projects. You want something that handles OAuth. You want something that handles Facebook Connect. You do not want something that handles "integration with social networks" or anything so grandiose.

[FlemishBeeCycle]

There's definitely a tendency among library/framework writers (not just Django) to include the kitchen sink. Ultimately it becomes problematic for the end-user and maintainer because more time is spent trying to understand everything that is going on (and often times removing unwanted functionality).

It's really hard to find functionality in the "hammer,screwdriver" size - more often than not I get a whole tool set with all sorts of things I'll never need, and end up having to devote more time figuring out how it all "hangs together" with the rest of the system.

It becomes a matter of whether you end up piecing your system together block by block or chiseling away to your end product.