Hardest part about designing good software is pricing in potential future needs. Easy to optimize a piece of code while making it impossible to change the spec, or design clean abstractions that will be circumvented once you add a new concept. Anticipating possible futures is key

→ View original post on X — @gdb,