Build a quiz challenge part 2 , written in 33 lines followed DRY concept, without creating 2 arrays please comment

Oh yeah, that's pretty slick. Have you played around on Code Wars ? You should! You'll see that on Code Wars, it's possible to vote a puzzle's solution as "clever". This is sort of a back-handed compliment in programming. It usually means that the code is very DRY, even if it requires using parts of the language that are obtuse, or the code is more difficult for humans to read. A "clever" solution means "yeah, that's cool, but I would probably never do this."

When writing DRY code, it's important to remember that the clever answers do not score you points in real life. Often times other people will be reading, proofing, updating, or otherwise trying to improve your code. VERY often that person will be YOU several months after writing it. DRY code is very important, and a good rule of thumb, but it should never come at the expense of being easy to read.

For example:

for ( var i = 0; i < questions.length; i += 1 ) {
  question = questions[i][0];
  anwser = questions[i][1];
  response = prompt(question);
  response = parseInt(response);

is not IMMEDIATELY clear. This code is very tidy and DRY, but it requires the reader to interpret two "at" notation levels, which is a bit confusing. I had to reorient myself -- remind myself that you have a nested array -- and think a little extra about what each [] refers to. Sometimes you want this for performance purposes -- if the code is substantially faster for being shorter. But most of the time, the performance boost isn't worth the confusion you doom yourself to later.

It's great to practice writing super DRY code in these exercises, and in places like Code Wars. It makes you a better programmer! But when writing production code, always prioritize human readability whenever possible!

Does that answer your question? If so, please up-vote my answer as "Best Answer"! It helps me reach my career path goals quickly. If not, feel free to write more!