If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...

If you have a not-so-usual solution for your problems but need to justify it to your boss...

If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...

...then 'No Bugs' Hare on Soft.ware might be the right place for you.

Your mileage may vary. Batteries not included

When architecting a system, it is inevitable to make certain high-level design decisions.

Some of these decisions, if they’re wrong, can lead to the re-architecturing and re-writing of the whole system some months later, so there is an incentive to keep things rather generic. On the other hand, trying to make system too generic is just another recipe to disaster (usually expressed in terms of missed deadlines and unmanageable code).

IT Hares try to describe certain not-so-obvious architectural decisions, and some considerations which should be kept in mind while making them.

Design Decisions, page 4:

Overused Code Reuse

posted March 1, 2011 by "No Bugs" Hare

Abstract:	When done imporerply, code reuse can cause severe problems, including loss of life.
Quote:	“Reusing code from other projects or (even worse) from 3rd-parties SHOULD NOT be taken lightly. Or else…”
	[→]

From Occam’s Razor to No Bugs’ Axe

posted January 1, 2011 by "No Bugs" Hare

Quote:	“Fight Features. …the only way to make software secure, reliable, and fast is to make it small” — Andrew S. Tanenbaum
Another Quote:	“If you do not have a concrete case of how a feature will be used – do not provide it. Yet.”
	[→]