It turns out that most of the time it does need to be that complicated. Especially with anyone who isn't just a raw junior developer.
It turns out that most of the time it does need to be that complicated. Especially with anyone who isn't just a raw junior developer.
If a legitimate feature is complex there's very little you can do. Apart from push back on the implementation specifics.
Quite often, code is too complicated due to it needing to interact with other problematic code.
So you could spend many times longer fixing all the underlying complexity and hopefully make it better.
Or just accept that it's not perfect, which while regrettably is the pragmatic choice (Until things get so bad it isn't)
Trying to make a "good" architecture when there are no sane way to do it in a good way is one of the deepest sins in my experience.
What a messy out of necessity implementation needs is seldom another layer of abstraction to mess with your head.
But realistically, just a handful of the real world scenarios we all face fall into this category of "least worse arch is black magic". I'd bet my house than 90% of the architectural problems we faced exist because of a poor process on understanding requirements or poor architectural design. In no small amount due to hese two things being very hard.
So the design itself needs to be questioned.