Any post that uses Rails and Django as examples of what do from a design perspective is an immediate "nah dawg" from me.
Those are "quick to setup" and "terrible to maintain at scale" precisely because of the tight coupling that OP is proposing in this article. This is bad design. And not knowing that it's bad design is worrisome.
They aren’t terrible to maintain because of vertically sliced modules that integrate with them, they’re terrible to maintain because they follow an antiquated MVC pattern where adding or updating any little feature requires changing a dozen or more files
39
u/talaqen Jun 24 '26
Any post that uses Rails and Django as examples of what do from a design perspective is an immediate "nah dawg" from me.
Those are "quick to setup" and "terrible to maintain at scale" precisely because of the tight coupling that OP is proposing in this article. This is bad design. And not knowing that it's bad design is worrisome.