3 ms·
To use a db efficiently you need to have a bit of an idea of what it does inside. You need to have a bit of an idea, sure. But in order to give any kind of a
by kafkaesq 9y ago
To use a db efficiently you need to have a bit of an idea of what it does inside.
You need to have a bit of an idea, sure.
But in order to give any kind of a meaningful answer to the question, you need to have not just a "bit of" an idea, but in act, a deeply solid and intuitive idea. Either that or -- crib the answer from websites like these, know that it's one of the top 30 questions you're likely to be asked.
Which, very sadly, is exactly what the modern interview process (greatly) incentives people to do, these days.
- neeleshs 9y ago"Meaningful" in an interview question does not have to be "correct". These questions can be used to evaluate the thought process, rather than for "ha! Wrong answer!". Questions are not inherently bad. It's how the interviewer interprets the answer, and whether it's used as a gateway to a discussion or a one way q&a session.
- aidos 9y agoDon't get me wrong - it's not a question I'd ask myself, but I think you'd get some interesting answers. I'm fairly sure with that starting question I'd be able to have a conversation that gave me a pretty good idea about how well someone knew databases. Do they talk about tables? What about indexes? How about sql? Do they ask enquire about the requirements / data model?
- marcosdumay 9y ago> Do they talk about tables? What about indexes? How about sql? Interesting, because as soon as I got over the "why the hell do you want to create a new DBMS?" question, my first thought was about filesystems. I haven't digged into any DBMS to look at, but all those you point look so easy when compared to atomic data writing...
- mlnj 9y agoIf someone started with 'How would you write a database?', I would just talk about simple csv reader n writer with no other promises and be done with it. Everything else is a feature.