Broke the puts feature out of convert method

Took the puts line out of the convert_seconds_to_years_and_months method
and created a dedicated for printing/puts.  Ammended the ages_in_seconds
iteration to contain new prints_age method.
Make 2nd challenge more modular by breaking out convert methods

Took the original convert_fahrenheit_to_celsius and
convert_celsius_to_fahrenheit methods and broke out the precision and
printing features from them.  Turn these into two stand alone methods:
make_precise_to_two_decimal_places and print_converted_temperature.
Gained more modularity, but lost the ability to print a more specific
statement, letting the user know what they originally converted from and
to.  Now the printed line just states the converted temp.  This could be
accomplished with a hash being assembled and passed.  Might look into
this later.
Created variables to replace the absolute zero temps

Created two absolute zero variables, one for Celsius and one for
Fahrenheit.  Replaced the values in the methods with these variables.
This is to make the code more clear and understandable, as it could be
confusing to see a random number like -459.67 repeated in the code a few
times.
Completed and clarifying exercise 1

This contains a method that uses string interpolation to read and
ultimately print a string.  I use the double quotes which creates a
string literal so that the string interpolation and the escape
characters will work as expected.  This prints one line at a time
because of the \n character being recognized, so it does have a line
return at these places; however, it does not pause in between printing
out each of the three lines.  Should it?
Exercise 3 / week 3 is done, but needs work

I believe I met all of the specs from the exercise, and did so in a way
that integrated things we have learned.  Like the ternary operator and
the '%04d' % some_number technique.  Integrating these techniques was
primary, and elegant code became secondary, I think.  This could
probably use some refactoring.
Figured out exercise 1 by investigating all the string methods

I went to www.ruby-doc.org and read through all of the names of the
methods, and did trial and error over and over with a bunch of methods
until I found something that showed a glimmer of hope.  This was the
split method.  I then remembered the prepend method that I had come
across.  I combined those two with the an iterator loop (which we have
not learned about yet, I know), and was able to get the desired
results.
Completed exercise 2 but still unclear on the answer

I ran this code to try to understand what is happening (below). As you
can see from the output, in the second method call, the before number
and after number lines are not part of the output. So obviously in some
way the method is arriving at the number 2.

I had hoped this technique would shed more light on why it is doing what
it is doing, but unfortunately it did not.
Add exercises 1, 4,5, and 6 from beginning of week three

Should have been doing more commits.  And more thoughtful descriptions.
My bad.  Will work on it.
Rubydoctest is a minimum testing framework

We actually can paste in the IRB session if we load our file and test
our "library", as comments, and use rubydoctest <filename.rb> to ensure
that our newest version of Ruby doesn't break things I have already
learned, or how my programs work.
Getting ready for more testing
Deaf Granny is starting to come together
Go over the doctest structure

We modified how we expect hello to work when asking if someone is there.