Some people have the "f**k DDD, f**k hexagonal, f**k everything" attitude and claim that pretty much everything except for coding itself is overly complex and a waste of time.
The article is explicitly not targeted at this group 😉
I get it. I wonder though if some of that attitude is push back on overly prescriptive patterns before they understand what problem they are solving? Esp in UI, I prefer to help move someone’s solution into the opinions of our system as opposed to forcing their solution into the opinions.
You know it (truism alert): the truth is somewhere in the middle.
The attitude mentioned is somehow extreme. The opposite extreme (e.g. "praise this paradigm" is same bad)
BTW the more you dive into any topic, the more you understand the "why", "why not", "when not" - and not necessarily the "how".
That was a nice read, thank you.
Also I was trying to come up with a smart reply, on how file based routing could introduce overlaps with architecture, but at the end it’s still just an implementation detail
Comments
The article is explicitly not targeted at this group 😉
The attitude mentioned is somehow extreme. The opposite extreme (e.g. "praise this paradigm" is same bad)
BTW the more you dive into any topic, the more you understand the "why", "why not", "when not" - and not necessarily the "how".
Also I was trying to come up with a smart reply, on how file based routing could introduce overlaps with architecture, but at the end it’s still just an implementation detail
BTW not only routing, but also lazy loading, area of responsibility, semantics boundary etc.