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 belief is most of the time a source of problems.
On the other hand, bold dares to create something you believe in can lead to something great.
But the ratio is relatively low.
@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.
@reduz It's a silent traps that can saps away your productivity without you realizing it
@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