#learnrubythehardway

[simplehacks]

Rules for if-statements (Ruby)

Every if-statement must have an else.

If this else should never run because it doesn't make sense, then you must use a die function in the else that prints out an error message and dies, just like we did in the last exercise. This will find many errors.

Never nest if-statements more than two deep and always try to do them one deep.

Treat if-statements like paragraphs, where each if-elsif-elsegrouping is like a set of sentences. Put blank lines before and after.

Your boolean tests should be simple. If they are complex, move their calculations to variables earlier in your function and use a good name for the variable.

(Source: Learn Ruby the Hard Way)

[mycodelog]

Tonight I did more exercises from "Learn Ruby the Hard Way". The examples provided are practical and the extra credit section provides a good challenge. 

Things of note : 

print vs puts

\\ acting as an escape sequence to make sure Ruby prints things appropriately when dealing with characters inherent in the language.

<<NAME can be working as a string but allows you to put unlimited lines of text rather than breaking it up line by line and will complete when you type NAME again in all caps. 

when creating something interactive, it is possible to source user input by using the gets.chomp() command, when this is assigned to a variable it allows the user to input the variable. 

require and include will allow you to add libraries / feature sets from other sources (ruby gems, programs, etc...) to your program. 

ARGV is the argument variable. it is a constant which means its' value should not be changed after being assigned. It assigns whatever argument you create to particular variables in your application.