Re:Django and Postgres for the Busy Rails Developer
by robertlagrant on Friday December 13, 2024 @04:39AM
(#42407235)
I'd say you should be able to quantify it. "a domain model tightly coupled to CRUD primitives" is not an intrinsic evil. If you were to genuinely save money or reduce risk by, say, moving off a relational database you would just need to pick that point and motivate for a rewrite.
The much higher risk IMO is building a hyper-flexible application from the start knowing what you need today is a CRUD app, just in case in future you need something else. That's how you get shelfware and awkward conversations.
Re:Django and Postgres for the Busy Rails Developer
by bigfatkitten on Friday December 13, 2024 @02:59PM
(#42411782)
If it was really pure CRUD you'd use Airtable or some other no code tool instead, and save yourself a ton of time and effort.
One of the problems I find is gradually complexity creep from the business. It starts off as a little clean method here, a signal there etc. Before you know it you've got a domain model tightly coupled to CRUD primitives.