Recent searches
Search options
I always believed that your worst enemy as a software architect is the belief that you add a feature because "you or somebody will probably need it in the future".
Even if it can happen, my experience was always that the more pragmatic you can get with problem solving, the better (and far more maintainable) the code produced.
I strongly believe that future proofing is a trap, but realize that its not easy to get into a pragmatic mindset.
@reduz for every feature you add, find one you can remove or replace.
Only add a feature if there is considerable pain without it.
Correctness, performance and developer comfort are features nobody explicitly asks for but are the foundation on which to build.