Recently I've read "Mythical man month" and one of the interesting perspectives to me is, that complex software is not built but grown. Top me that makes a lot of sense. You don't start out with a perfect blueprint and implement but rather start with a prototyp, turn it into a minimal viable product, mange technical debt, explore new features, adapt to changing environments and so on. The code base is like a garden that needs care and yields utility. This perspective also helps me with frustration in legacy code bases. Working in a garden is nicer than working on a construction site. It also resolves the question of when the software is finished. It will always need maintenance. It can always be developed further.