I liked this article, but one point it misses is that you should be solving problems in a way that makes it easy to keep solving problems in the future, and tha

I liked this article, but one point it misses is that you should be solving problems in a way that makes it easy to keep solving problems in the future, and that's a tradeoff that even more people get wrong. For instance, writing good, maintainable code only matters because if you don't, you might reduce your ability to solve more problems in the future when the problems you need to solve might change, due to learning new information about your users/customers, your users/customers changing, etc. For example: - the code itself might be difficult to understand, reason about, and change, making it hard to make changes. - the code might require time spent on maintenance, which reduces the time you can spend making forward progress.