On the topic of good code, yes it should be understandable to the reader. I used to think about good code in terms of various principles and maxims, but with m

On the topic of good code, yes it should be understandable to the reader. I used to think about good code in terms of various principles and maxims, but with more experience I feel like the story of requirements is overlooked. When requirements were static from the beginning and easy to understand for all parties you can get good code. It kind of exists in a bubble of stability. And when you reach for it again the stableness is unchanged so you just forget about it and it becomes part of the background noise. Much of the time the tech debt and weirdness of codebases I encountered in the wild is a reflection of an untold story of how requirements changed and miscommunication between the parties involved