You are fortunate if you only have to explain it to juniors. This seems pretty prevalent among senior developers too, in my experience. The most egregious cas

You are fortunate if you only have to explain it to juniors. This seems pretty prevalent among senior developers too, in my experience. The most egregious case was, this guy I worked with, who would just straight up start with abstractions to avoid any duplication and enable other use cases. Now, 9 out 10 times the use cases catered for by the abstraction failed to materialise (bloody customers) but boy did he let you know when he hit the abstraction lottery and what he'd done neatly fitted in with a new use case. I think the term for what he created was ravioli code although maybe some of it was lasagne code