Thinking about how any useful software system has a lot of complexity, and the ways software developers cope with that complexity
One classic is "find a similar feature and just search and replace", because that way you don't have to understand the system
Another is "give up on understanding the system and try to build a new system that does more or less the same thing (usually less)"
Another is "ask someone else how it works endlessly without trying to understand it yourself" (There's a guy at my work who does that last one and it gets pretty annoying - and it feels like I understand things better than him, even though he's been there for years longer)
I think there's something to be said for embracing the complexity as a necessary part of a useful system, rather than as something to be eliminated or avoided
