2 ms·
Developer discovers there's a difference between the declarative paradigm and the imperative paradigm, writes blog post, news at 11. Snark aside, you can take
by henrikschroder 15y ago
Developer discovers there's a difference between the declarative paradigm and the imperative paradigm, writes blog post, news at 11.
Snark aside, you can take the author's advice too far in the other direction as well. Relational algebra is all fine on paper, but relational integrity, foreign keys, strict normalization and n-way joins are horrible for performance. At the end of the day, the declarative SQL you write has to translate to a bunch of bulk reads from a hard drive somewhere, and you really need to understand execution plans as well if you want any sort of performance.
- cbsmith 15y agoTHIS. I was going to write the same thing. It's really about declarative/functional programming vs. imperative/procedural programming. He's right though that as you work with more and more data, the impact of making the traditional imperative/procedural mistakes because a real problem.