###Leap
- [This] (http://exercism.io/submissions/7011c3076ed947af9a40b3e49231a3b3) solution is very similar to mine, except that it (and most if not all of the examples to follow) use prototype to create the method on Year, rather than this. After doing some reading, I think that I understand why this is a better choice.
- [Sal's] (http://exercism.io/submissions/89610e20a7074240b60265819e275dd7) solution is more verbose than mine but I like that it clearly follows the language of the instructions for the problem, in that the if statements progressively exclude years that fail to fulfill leap year conditions.
- [Jon's] (http://exercism.io/submissions/23876f6a24734226a0b2ae881868f780) solution is very similar to mine, in that it returns the boolean result of a single of code.
- I like that [this solution] (http://exercism.io/submissions/51762f2d1cbe4ba2b09fde8dbf2a601d) removes the redundancy of the and/or statement and uses a clearly defined method to improve the readability of the code. I didn't think to replace the % operator with a method, but I can see the benefits. I strongly object to the use of 'dividable' though.
- Mark's solution is very similar to the way that I initially solved this problem. It is lengthier, but it is also easier to read at first glance.
- Ling's solution is way cooler than mine. I like the idea of using the dictionary variable and think that it makes for much less convoluted looking code.
- This solution is the most similar to mine that I have seen. I think that I defaulted to case because of experience with long if/else methods in ruby, and though case isn't shorter, it does seem a bit clearer at times. The formatting of this response is easier to read, but I think that the variable is poorly named.
- This solution is very similar to Ling's, but I like that they passed the character from the DNA strand directly into the translating dictionary. I thought that the dnaLength variable was extraneous, though.
- This solution is a simple and straightforward use of if/else statements. It is very clear and easy to read.
- This solution is the best that I was able to find, combining the dicitonary with regex to map over the DNA sequence, which is very clever without being unclear.
###Hamming
- Sal's solution is a more condensed version of mine. I like that it's readable, and I could defintitely have named my variables better. Though it adds several lines to my code, I like immediately excluding strands that are the same.
- Ali's code reminds me of doing this exercise in Ruby, because an immediate criticism that I received was about splitting the strands into characters. Though it absolutely makes human sense, I don't think that the extra step serves any purpose other than making it easier to imagine the strings concretely. Which is weirdly comforting, but inefficient.
- This solution is almost exactly the same as the others listed, but I really disliked that s/he named the strands 'left' and 'right.' I found it confusing even though I knew what problem they were trying to solve. I should probably keep this in mind when naming variables unclearly.
- Ling's solution broke more of the logic out into named methods, but I'm not sure that the result was much clearer than a simple and sequential if/else clause. I like the idea, though.
- Josh's code - same comments as Sal's