Re:That won't scale Or present cost vs. future value
by antoineMoPa on Sunday April 23, 2023 @11:04PM
(#35683225)
In the first example, you have to implement the file reading approach now, then the database reading/writing approach, plus a migration script. You did extra work that you would not have done with the DB-first approach (migration + the initial system that goes to trash)
In real life, as projects get more complex, the migration + initial system cost is so high that I'd rather come up with a clean architecture first. Also, it's more fun as a programmer to know that you are not working on a dirty solution.
Also, in real life, if we scale up these examples, maintenance cost can be higher for the dirty solution.
In real life, as projects get more complex, the migration + initial system cost is so high that I'd rather come up with a clean architecture first. Also, it's more fun as a programmer to know that you are not working on a dirty solution.
Also, in real life, if we scale up these examples, maintenance cost can be higher for the dirty solution.