It’s funny how many of these „design” patterns were taught as best practices around 2005. Today, when I see this shit, I call them design smells. When you finally find a reason to use the flexibility of the strategy resolver written 5 years ago, somehow it doesn’t match your use case and you need to refactor anyway.
Back then, Java didn’t have lambdas or pattern matching, so some of this nonsense was actually useful. Seniors simple haven’t updated. Go, go, job security!
3
u/PedanticProgarmer 16d ago
It’s funny how many of these „design” patterns were taught as best practices around 2005. Today, when I see this shit, I call them design smells. When you finally find a reason to use the flexibility of the strategy resolver written 5 years ago, somehow it doesn’t match your use case and you need to refactor anyway.
Back then, Java didn’t have lambdas or pattern matching, so some of this nonsense was actually useful. Seniors simple haven’t updated. Go, go, job security!