4 ms·
> I think this is normally due to bad requirements or bad architecture. Trying to make a "good" architecture when there are no sane way to do it in a good way
by rightbyte 4y ago
> I think this is normally due to bad requirements or bad architecture.
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.
- rapnie 4y agoScott Wlaschin mentioned this nicely (I think in "Domain models made Functional"). Paraphrasing: "You can have all the nicest tools and greatest libraries and frameworks and coding skills.. if garbage goes in, then garbage comes out".
- sebastialonso 4y agoThat's precisely why we should stop thinking about "good" architecture. At the very best, we'll find the least worse architecture, and that's that. 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.