Merely removing features is not deep enough. This is fundamentally at its
origins an architecture challenge, and a development management challenge.
Removing features is rearguard action, not properly conceived engagement
with the problem.
Complexity can be neutral; code size by itself is not
On 15-04-22 05:06 PM, George Herbert wrote:
He does not seem to understand the harm of
complexity, and does not here appear to understand the role that singular
architects and dev leaders and style guides and code standards can have.
I'm pretty sure I disagree with this. Any system will begin
At those sizes, insisting on APIs between component levels/layers/areas
helps keep sanity and order.
Every system's complexity reflects both actual functional requirements, at
whatever level of simplicity was realistic to impose, and evolution of the
required features as the uses were expanded
