What I Did

As with yesterday, today I had a large chunk of me time in which I was able to focus on my own work. Namely, I’ve gotten sign-ups and login functionality good to go, despite lacking tests for said models whatsoever. To that end, Eli has gotten me started with using RSpec in place of Rake’s so that I may embrace behavior and test driven development the Viget way.

What I Learned

Aside from keeping to myself, I had another highly productive session with Eli in which he fleshed out the db/schema.rb file, the difference between embedded Ruby tags <% %> and <%= %>, what exactly the render function does and how it’s implied in controller actions, and factory girl to serve as a replacement for fixtures (similar to how RSpec takes the place of Rake’s testing capabilities)

What I Still Don’t Understand

I am still shaky on exactly where to place functions that you wish to use in various controllers and views. As of now, I’ve defined log_in and log_out functions within a module called SessionsHelper which I’ve included in ApplicationController. So far, I’ve not run into any errors, having called those functions in both my SessionController class and my _header.html.erb partial which requires the function to determine what links to include in the nav bar depending on login status. Also, there are a few git merge concepts that are ambiguous to me. On a whole though, I was able to successfully execute a couple of rather precarious git merge operations.

What I’m Interested in Learning

This is slightly beyond the scope of my current task at hand, but now that Justin has lent me his Pebble watch, my Startup Colorado team may do some work requiring functional programming, and Eli had recommended to me to do this way before the internship, I am really interested in dabbling with JavaScript on top of my current focus on Rails.