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 I have been writing a booking system for the last 10 years and the amount of stuff I wrote in the beginning because it may help me later was wayy too much.
If you've run something for several years without running into the edge case you prepared for it's Ok to leave the implementation of that feature to "Future You".
They may be mad at you, but most likely they have an even better understanding of the problem and the best solution then anyway