3 ms·
> 5. Tedium is Inescapable. No O/R-mapper or code-generator can ever solve the fact that records, fields, validators, etc. need to be defined, by hand, in at le
by anamax 18y ago
> 5. Tedium is Inescapable. No O/R-mapper or code-generator can ever solve the fact that records, fields, validators, etc. need to be defined, by hand, in at least two places (front- and back-end). A UI generated from the database is just as bad as the database that’s generated from the UI.
Tedium may be inescapable, but defining something multiple times pretty much guarantees that at least one of the defintions will be wrong and usually takes more time than defining said something once.
Normalization isn't just for databases.
- kragen 18y agoI basically agree, but there's a certain amount of sense in the statement you're debating — if I design either the database or the UI and then make the other one just a thin layer over it, I get a terrible database design or a terrible UI design. I haven't found a good rapid-feedback way to design them both in a single representation, and so I end up editing code in at least two places when I want to add a field. Do you have any suggestions about what kind of software you use that avoids that?
- anamax 18y ago> I basically agree, but there's a certain amount of sense in the statement you're debating — if I design either the database or the UI and then make the other one just a thin layer over it, I get a terrible database design or a terrible UI design. Then don't do that. > I haven't found a good rapid-feedback way Is rapid more important than correct? > Do you have any suggestions about what kind of software you use that avoids that? They're both scriptable.
- kragen 18y agoI am disappointed in the quality of your response.