Similarly, I've found that keeping the need in mind that the code addresses helps keep you focused on what is core vs non-core. It also helps create a useful pr

Similarly, I've found that keeping the need in mind that the code addresses helps keep you focused on what is core vs non-core. It also helps create a useful product that someone will want. Apart from not having complexity in the first place, the next best thing is to recognize that software is a theory, and try to improve your understanding. Treat the first version as a learning experience, trying to understand the problem: Plan to throw one away, you will anyway. (Brooks)