Maybe you often add too many things and get into a complexity nightmare that way. I often err too far the other way, skipping working on boring-but-important gr

Maybe you often add too many things and get into a complexity nightmare that way. I often err too far the other way, skipping working on boring-but-important groundwork features, I try to press on without them, making life too hard for myself. I tend to justify this avoidance as I’m keeping the system ‘simple’ but then I end up stupidly creating more complexity to work around not having the sensible/useful thing I’ve been avoiding adding. So for you, YAGNI is a useful corrective notion to try to keep in mind. For me it’s playing to my worst instincts. This is the case for all one-sided and unbounded advice like YAGNI. It is useful for people who need to hear it and harmful for those who don’t. I prefer the idea of “everything should be as simple as possible, but no simpler”. The last bit is crucial for me and is missing from “YAGNI”.