As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
As i am in between 1-2 years experience what should i say to this interview question....
What are the types of Normalization?
Should i say all the normal forms or what?
Way too broad of a question for an interview - it could fill a small book. I would simply remember a few key points about the first 3 normal forms (4 and 5 for extra credit). Here's a somewhat decent summary of them.
If I were interviewing you, and asked the question, I would want to hear above anything else that most db designers strive for at least 3NF but should be able to deviate from that for X reasons. Knowing when to stray from normalization and why is way more important and telling than knowing the definitions.
Knowing the formal definitions of the normal forms and being able to give some real world examples would be an excellent answer to the question.
FWIW, I think it's a silly question to ask except when interviewing people straight from a University where there's not much to ask for but theory. One of the 1st things they taught me when they taught normalization was "we'll explain these [normalization] steps now, but keep in mind that once you understand it, you won't think in terms of normal forms because 3NF will come naturally". And they were right.
Much better interview questions would be "what's wrong with this schema?" and "design a schema for the following data...". because they show applied, practiical knowledge of the underlying principles.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
My question seems to be dump, but because i was studying this new technique, i've found that NoSql has changed from its beginning, for example, in the beginning there was the problem of see your own update, and for example Facebook dident let users to update their comments due to the write once, read many
So, do i change all concepts that i've read in 2010-2012 tutorials?
Has NoSql beat the CAP theorem ?
I agree this can easily turn into discussion. I'll give brief answers from my experience to your two questions:
No, the concepts haven't changed. The landscape seems to be growing quite a bit as lots of companies get into the NoSQL space. Beware vendor promises!
No way. Just read this article this morning, it is a great explanation on some of the issues with the CAP theorem: http://codahale.com/you-cant-sacrifice-partition-tolerance/
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I've been looking around for a Mortgage Payoff calculator and it looks like the ones that are available are primarily commercial. Does anyone know if it already exists somewhere in script form that could be translated into another language?
If not, is anyone familiar enough with the logic that wouldn't mind sketching up the pseudo-code? I'll be able to script everything together once it's laid out but all searching I've done so far has only turned up results for creating an Mortgage (not payoff) calculator.
In addition to the obvious utility, hopefully putting this logic out there will help people better understand how their mortgage is being calculated.
http://www.r-bloggers.com/mortgage-calculator-and-amortization-charts-with-r/
The amortization shows you the remaining principal which is the same as the payoff amount.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
As per the article at W3Techs, Perl ranks the lowest among the server side scripting languages, even less than Java? Is there any reason behind it? Perl, as far as I see, is very popular, and an awesome language, how come it is hardly used by websites? Does it have issues with server side scripting?
This article has a lot of details on how W3Techs gets their data: http://w3techs.com/blog/entry/usage_of_perl_for_websites_fell_below_1_percent
As i did some analysis on this, let me summarize in short that the data presented by W3Techs is deeply flawed and extremely misleading. First off, it is important to know that they detect technologies of sites by running simple scripts at them that look for file suffixes in urls and then just take that and never verify with the site owner. As such they have a "no-detect" rate of 17.6% (plus an unknown "false-detect" rate). A more correct version of their chart would be this:
If you'd like to get more details and more mistakes in their data methodology, please take a look at the comments of the article, especially those written by "Mithaldu" or "Christian Walde", i.e. me. I posted extensively there as to why their data is nearly useless and why they're even misinterpreting the data they do have.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I know I am asking two questions in one. But can someone please tell me what is meant by bigdata. Also how does NoSQL different from conventional SQL.
Lastly can you please recommend good/best books or tutorials/website on topic which can take a newbie to advance level.
Please reply.
"Big Data" is a buzz word, which means that it defines different (albeit related) things to different people.
Some use it for database software that specializes in "Big Data", some use it for whole infrastructure that manipulates large data sets, some use it for large data sets themselves (structured, semi-structured, and non-structured).
"Big Data" data sets posses at least one distinct property: due to their large size and/or lack of structure they are assumed to hide valuable information and relationships. The end goal of about every "Big Data" project is uncovering these valuable knowledge in efficient and repeatable manner.
How large is "Big Data"? Large enough that few years ago it would demand million dollar investments in all 3: hardware, software and development. Today you may still require a significant (but less) investment but probably just into 2 out of these 3.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm completely new to Modelica and was wondering what is the best way to learn on my own? Also I will be using it with MapleSim 5 (or 6 when it will be available) so any information regarding that would be helpful too.
I'll need Modelica to create a few components for a thermal model, then simulate with MapleSim and hopefully I will also manage to co-simulate with another software (EnergPlus) using FMI when it will be available for MapleSim and BCVTB.
Sorry for not being specific with my question, really any reference to a good Modelica guide would be great, thanks.
Clearly, I am biased, but I like to think that my book "Introduction to Physical Modeling with Modelica" is a great way to explore the features of Modelica in the context of engineering problems. I noticed that Wolfram seems to recommend the book as well.
But in the interest of balance, there are two books by Peter Fritzson on the topic of Modelica as well.