= 27d567bc2d48d9f40e9ccc20ea370b15)
Daniel_Burfoot comments on How to Learn from Experts - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (10)
Well, it depends on the architect, I suppose. I would say "write your application in a modular way so that it doesn't rely on specific features of the underlying database, and if you need to make exceptions to this principle, make sure the relevant code sections and dependencies are well highlighted and documented."
I agree that as much as possible you want to make things modular, but good data processing code for a relational database is going to be really different than good code for a distributed key-value store or a mapreduce+cache setup.
Good call. This is a great example of how sometimes experts can even point out that you're thinking at the wrong level of abstraction, and provide a better one.