fix

source/2013-03-02-Eloquent-ruby-final.html.markdown

@@ -1,11 +1,10 @@
 ---
 title: Eloquent Ruby- Final Thoughts
-date: 2013-03-08 13:19 -07:00
+date: 2013-03-02 13:19 -07:00
 ---
 
-We turned in Traffic-Spy yesterday.  This project introduced us to both web frameworks and databases, and having constructed a functional product, I feel pretty good about what my partner and I accomplished.  I should say though, the actual web site which displayed the information we were tasked with gathering and sorting, was hideous, there is no denying that.  After getting familiar with sinatra and postgres, we simply had no time to try and figure out enough html and css to make our site display anything more than raw data.  I expect, our next book "html & css", will give me the information I need to make my next project a bit more professional looking.
-
-As I mentioned above, this was our first project using a database, so while my team did manage to build a functional app, I wouldn't say that I have a complete understanding of them.  For me, the leap from having a file containing all the data that my program needed, to having that data stored in some dark, far-away corner in the bowels of my computer, was pretty significant.  At this point, I would say knowing how and where to specify which database to use is what I am still a bit unclear on, but I think that I will be able to get that straigtned out before the end of the next project.
-
+Eloquent Ruby did a good job of expanding my understanding of some of Ruby's core concepts.  Throughout the book, there was a good mix of theory with specific code examples.  I never found myself wondering what a method being discussed actually looked like in practice for too long before I came across an example.  The examples themselves were nested within rich explinations of their use and strategic applications.  The first couple of sections of the book were probably the most helpful, as they covered the topics that I already had a decent understanding of.  These secitons opened my eyes to new uses for these familiar methods and their overall functions, but even when I read about concepts that I didn't understand, I could gather enough about why they were important to want to come back later.
 
+At this point, I feel like there were many such concepts that went over my head, but the way the information was presented definitely got me interested.  I look forward to being able to re-read these sections down the road when I will have had sufficient experience to pick up on the finer details of what Russ is talking about.
 
+I would definitely recommend this book to someone who is atleast where I'm at in terms of Ruby experience, but I think it would benefit someone who is a litte further along more. As I mentioned above, I feel like I got the most out of the sections of the book which covered information that I was the most familiar with.  The sections which covered less familiar material were great, in that they got me excited for what lies ahead, but probably won't be terribly usefull in the short-term.

source/2013-03-08-TrafficSpy-retrospective.html.markdown

@@ -1,10 +1,9 @@
 ---
-title: Eloquent Ruby- Final Thoughts
-date: 2013-03-02 13:19 -07:00
+title: Traffic Spy Retrospective
+date: 2013-03-08 13:19 -07:00
 ---
 
-Eloquent Ruby did a good job of expanding my understanding of some of Ruby's core concepts.  Throughout the book, there was a good mix of theory with specific code examples.  I never found myself wondering what a method being discussed actually looked like in practice for too long before I came across an example.  The examples themselves were nested within rich explinations of their use and strategic applications.  The first couple of sections of the book were probably the most helpful, as they covered the topics that I already had a decent understanding of.  These secitons opened my eyes to new uses for these familiar methods and their overall functions, but even when I read about concepts that I didn't understand, I could gather enough about why they were important to want to come back later.
+We turned in Traffic-Spy yesterday.  This project introduced us to both web frameworks and databases, and having constructed a functional product, I feel pretty good about what my partner and I accomplished.  I should say though, the actual web site which displayed the information we were tasked with gathering and sorting, was hideous, there is no denying that.  After getting familiar with sinatra and postgres, we simply had no time to try and figure out enough html and css to make our site display anything more than raw data.  I expect, our next book "html & css", will give me the information I need to make my next project a bit more professional looking.
 
-At this point, I feel like there were many such concepts that went over my head, but the way the information was presented definitely got me interested.  I look forward to being able to re-read these sections down the road when I will have had sufficient experience to pick up on the finer details of what Russ is talking about.
+As I mentioned above, this was our first project using a database, so while my team did manage to build a functional app, I wouldn't say that I have a complete understanding of them.  For me, the leap from having a file containing all the data that my program needed, to having that data stored in some dark, far-away corner in the bowels of my computer, was pretty significant.  At this point, I would say knowing how and where to specify which database to use is what I am still a bit unclear on, but I think that I will be able to get that straigtned out before the end of the next project.
 
-I would definitely recommend this book to someone who is atleast where I'm at in terms of Ruby experience, but I think it would benefit someone who is a litte further along more. As I mentioned above, I feel like I got the most out of the sections of the book which covered information that I was the most familiar with.  The sections which covered less familiar material were great, in that they got me excited for what lies ahead, but probably won't be terribly usefull in the short-term.