Mod 4 Prework

javascript_exercisms.md

Leap

My Code

• Responder 1 - This guy has bascially the same implementation as me, but chooses to divide it out for "readability". I wonder if this is completely necessary.
• Responder 2 - The use of prototype here is very nice. Gets rid of returning the boolean value and the else statement.
• Responder 3 - I wonder if the separation of this one is a little much. Gets the job done but seems a bit verbose.
• Responder 4 - Someone needs to remove som comments. WOW. I don't understand the user of parseInt here and find this a little off from what the exercism was trying to accomplish.
• Responder 5 - Very interesting take here. I learned about a new way to write conditionals.

Hamming

My Code

• Responder 1 - I need to better understand the use of prototype. I also should've used ++ instead of +=. Very similar thought. The split seems unnecessary.
• Responder 2 - This is another person using split. I don't understand why it is necessary in this exercism.
• Responder 3 - I used throw new Error which is looks like I could've just done throw and pass is a string. Nice.
• Responder 4 - This one used nested if/else statements to determine if the lengths were equal. Different take on throwing the error.
• Responder 5 - Ummm. No.

Rna Transcription

My Code

• Responder 1 - I like the use of split and join here.
• Responder 2 - Different way to take it with case statements. A little verbose for my liking.
• Responder 3 - Line 7 is kind of crazy in this. So many functions strung together. Hard to read.
• Responder 4 - This is similar to my original approach before I thought of using a hash. I like the explicitness of it.
• Responder 5 - Using replace? Dang! This one seems a bit overkill for the problem at hand.