When doing software design, a common question is how much “advanced” functionality to build in, and how much to let the users create themselves using a simple set of tools. For example, a reporting module could have many canned reports, or could have a tool which allows users to build reports themselves (or both). [...]
Looking for skillful techniques that make it easier to build software well
Interesting recent reads- Some of Maryland's open source heroes
- Making ESB pain visible
- New Firefox Standard Aims to Combat Cross-Site Scripting
- Does the 'Hacker Ethic' Harm Today's Developers?
- Architecture makes Agile Processes Scalable
- EstimatedInterest
- The role of the Software Architect in successful projects
- Becoming more architecturally aware - part 2
- The bizarre assumption of functional decomposition
- SchoolsOfSoftwareDevelopment