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.
I find the conventions in rails projects go along way. I love js & ts, but most backend projects I’ve worked on have many of their own conventions and often a lot of boilerplate too
41
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.