#dry code

[timsandberg]

Intelligent Design

Today’s readings largely focused on good code design, with a few tips on Hash/Array instantiation (setting default values).  The exercises were two games: Mastermind and Hangman.  We accomplished the first game before lunch, and NEARLY debugged our Hangman before end of class at 6.

In both coding projects we strove to stay within more advanced coding guidelines:

Break out complex code in to small methods ( < 10 lines)

DRY: do not repeat yourself

Minimizing parameters

Avoid long method chains

In the end I was really happy with our code: its day 3 and I already see great progress in the way I approach problems and organize more complex programs.

Favorite Ruby tricks learned today:

Parallel assignent of n variables with array of length n ( x, y = [1, 2] ).  Awesome for cleanly passing data between methods

Deep copying a multidimensional array.  I had a problem with this yesterday in tictactoe trying to use the “dup” method.  Just needed to use map.  Its ALWAYS map…

[darshecodes]

WET and DRY code

the first thing I learned from Dev Bootcamp was to always try your best to implement DRY code...

Don't Repeat Yourself

as opposed to WET code...

We Enjoy Typing

The reason that repeating yourself in code is dangerous, is that it is much easier to make an error if you keep repeating yourself. It is also harder for others to read when they come into the code. The best way in my experience to solve this problem is to define the repeated code into a method, and call that method when necessary.