3 ms·
>I realized that many of the times you hear this phrase, it’s from someone who has not given the problem and all its subproblems very much thought. The author'
by coldtea 4y ago
>I realized that many of the times you hear this phrase, it’s from someone who has not given the problem and all its subproblems very much thought.
The author's point being that if you did give "the problem and all its subproblems" much thought, you'd agree on their proposed solution.
But there's also absolutely a problem of "giving the problem and all its subproblems TOO much thought".
That's how over-complicated, over-engineered, second-system effect, everything-and-the-kitchen-sink designs, and architecture astronauts' designs, come to be...
Sometimes you're just giving the problem and all its subproblems too much though, and solving the simple case will get you a Pareto 80% of the way there - or even 100% of the way there, and all the other issues you want to tackle are remote eventualities and edge cases you can just ignore without issue...
>Do not judge a solution as “over-complicated” until you fully understand the problem domain and every sub-problem that the business needs to be solved.
That's another issue: every sub-problem that the business wants to be solved is seldom every sub-problem that the business needs to be solved.
Requirements get blown up with BS all the time, to the detriment of business value, delivery times, etc. Sometimes by the customer (who just throws in stuff they think they need, or they might need someday), oftentimes by the sales people or resident architecture astronauts...
So, solving at an appropriate design level "the problem domain and every sub-problem that the business needs to be solved" doesn't mean your design isn't over-complicated. It might be properly-complicated for those needs, over over-complicated compared to what it should actually be, if the real needs where considered (as opposed to mere "business wants" presented as "business needs").
- karmakaze 4y agoThis is definitely a pattern that I see. What's often overlooked after giving the problem and all subproblems much thought, every problem detail has a corresponding implementation. A simple solution is one that can somehow group problem details conceptually then design a de/composition with natural seams and loose coupling. The difference in process I usually see is incrementally coding up a solution adding detail cases vs first mapping problem facets to concepts then factoring those concepts so the implementation has boundaries that follow the problem seams. Just because you can point to an aspect of the problem for every line of code that exists doesn't mean it's not over complicated. "Over complicated" is either an assessment by someone who doesn't fully understand the problem OR an inability to see or even imagine that a simpler solution could exist. Simple doesn't mean easy (e.g. add an 'if' somewhere in current design). Understanding is not only about coverage. A thing that I recently encountered is decomposing a problem top-down, and implementing the solution top-down, which lower-levels getting parts of the problem at hand unnecessarily leaking into it. Once I suggested to think of decomposing the problem top-down, but built the solution bottom-up from that envisioning, all the while trying to name concepts of the lower-level things and keeping them as free of unnecessary details at each level, things cleaner separation of concerns with deliberate interface points.