5 ms·
I don't really understand the thought process. Clearly, to know how they work at the low level you must also understand what they are (the superficial understan
by saurik 9y ago
I don't really understand the thought process. Clearly, to know how they work at the low level you must also understand what they are (the superficial understanding you are describing here). I don't see any harm from also knowing how they work, and as someone who has been using PostgreSQL for something like two decades I am extremely glad I do, so saying it is "better" to only know what they are at a superficial level instead of also knowing how they work at a deep level seems really wrong. Meanwhile, as this article notes in its first sentence, most software engineers in this article's target demographic use database indexes every day and we would be shocked if they didn't already have the superficial level of understanding. Now, I haven't verified this is a good article, nor is it clear to me we needed yet another article to explain this, but you seem to be coming from the idea that this knowledge shouldn't even be imparted?... from the perspective of an "IT educator"? :(
- elchief 9y agoI'm not saying it shouldn't be imparted, but the high level knowledge is better first People seem to get lost in the details. I know devs that understand the various index tree types, but don't understand why something is sargable or why dropping indexes before a bulk copy is faster
- Angostura 9y agoI simply assume that the article is written for people who already know what an index is.
- rusbus 9y agoOP here. That was in fact the case ;-)
- kbwt 9y agoI actually disagree. High-level knowledge without later filling in the gaps leads to cargo-cult software engineering. If people get lost in the details, they are not prepared to fully understand the big picture.
- MaxBarraclough 9y agoI'm not sure that applies to everything, though. I'm sure we agree there's a limit. Joel Spolsky is right when he writes about the 'Law of Leaky Abstractions', but I'm not sure the average CRUD developer needs to know the gory nuts and bolts of his DBMS. Of course they need to know enough to reason effectively about good design, performance, security, etc, and more low-level knowledge is always a good thing. As an extreme example, PHP programmers don't need to understand branch prediction and caches.
- tinymollusk 9y agoYou are very correct for anyone who would consider themselves a programmer. I was thinking in a bigger scope; with so many non-programmers working technical roles (and especially with data/databases), I think this is a marvellous way for e.g. project managers to have a brief mental model of what a db index is.
- amirouche 9y agoI think 'Law of Leaky Abstractions' is overrated. Abstractions always leak, the question is whether it is part of the API and explained or not. Another example that is not indices: async/await is a leak of the underlying implementation and inner working.
- MaxBarraclough 9y agoYou've mentioned an abstraction but not explained why it's leaky. I agree that async/await leaks in places, such as in the surprising deadlocks that Stephen Cleary explains. I've met more than one pretty serious C# developer that wasn't aware of this. http://blog.stephencleary.com/2012/07/dont-block-on-async-code.html http://blog.stephencleary.com/2012/07/dont-block-on-async-co... > the question is whether it is part of the API and explained or not More broadly it's a question of pretending things can be wrapped up in tidy self-contained entities, and the idea that we can fully design away the messy details of reality. See also the Three Big Lies of C++ https://youtu.be/rX0ItVEVjHc?t=17m15s https://youtu.be/rX0ItVEVjHc?t=17m15s