dagheti

8 ms·

31.
by dagheti 17y ago
I guess the tricky part here is defining the term "mostly written". My mistake for introducing it (and of course the tautological 'don't prematurely optimize'). Agreed, you should measure as soon as you can and it's best to be building and
32.
by dagheti 17y ago
Isn't the time for measurement usually after the code has been mostly written? Not prematurely optimizing means getting to the measurement point as soon as you can, then using actual profiling numbers to focus your attention on what needs t
33.
by dagheti 18y ago
I agreed with your overall point, but I was expanding on part of what you were saying: You seem to appreciate how Haskell allows you to separate your pure code from your non-referentially transparent monadic code. This gives you reasoning w
34.
by dagheti 18y ago
I agree with you here 100%. Maybe this is a good pathway to explaining why relational databases are good ideas in much the same way as having a programming strategy that uses a backbone of pure functions. This purity-dividend is exactly why
35.
by dagheti 18y ago
Ok so let's clarify this: (SQL schema & upgrades + ORM classes + Logic classes, random scripts) - (logic classes + random scripts) = SQL Schema & upgrades + ORM classes The question then becomes how do you handle the trade-off betwe
36.
by dagheti 18y ago
The flexibility of the relational model is built on its bare simplicity: values + sets + logic. If you propose adding to this and giving up the benefits provided by these simplifications (simplicity of reasoning, ability to change the physi
37.
by dagheti 18y ago
Hierarchies and graphs are both fundamentally navigational data models, which force a physical-logical coupling of concerns, hampering flexibility significantly. The network model recognizes the flexibility issue with hierarchies, however I
38.
by dagheti 18y ago
What do you mean by impressive "ease of execution"? How terse the code is? How easy the code is to read? How likely the code is to be correct? How flexible the data model is to new requirements? How simply you can reason about what the code