Post #2232189
2023-09-17 20:49 UTC
@silasmariner@hostux.social @jk@mastodon.social It's not that it doesn't work or is even unidiomatic, but that it has a tendency to develop around the problem and so be a long list of edge cases, borderline hacks, etc. That's why I think it's relevant to the thread, because it isn't the very "abstracted" style that is considered proper, where every problem must be solved for the (imaginary) general case.
Replies (1)
-
@berkes@mastodon.nl 2023-09-18 07:01
@tomw@mastodon.social, have you considered software architectures that adress this problem? My domains too are messy, fluid, and ambiguous. Aren't all? So I use #ddd to model this domain. Then anti-corruption layers to put the most ugly parts, or uninteresting (and their libraries and frameworks) behind curtains, to keep all that abay. Hexagonal architecture to abstract these layers. And events to bind everything together. @silasmariner@hostux.social