I'm a Floridian web engineer who planted his roots in Paris. Some of my favorite past-times are analyzing and optimizing development processes, building solid APIs, mentoring junior devs, and long walks on the beach.

Accidental Globals in JavaScript 09-25-2011

var thing = function(){
    var a = b = 0;


console.log(a);  //ReferenceError, that makes sense b/c 'a' wasn't defined in global scope
console.log(b);  //0, oh noes!! Looks like our multiple equals statement from line 2 sets 'b' implicitly as a global

Names n Stuff 09-18-2011

A few days ago, where I work, there was an argument over whether the following function should exist:

def is_premium_or_has_receipt_for?(product)
  self.premium_member? || self.store.has_receipt?(product)

I had a hard time explaining myself as to why I thought the function should not exist. At first all I could think of was, "This seems like a bad idea." Then I ran into a similar piece of code today and it became clear to me.

The function should exist, but there is a problem with the name. It simply restates what the logic is. When writing functions one of the benefits is that it allows you to group a bunch of smaller ideas into a bigger one. In this scenario we are merely re-writing an if clause in a prettier fashion; But the lines of code together are conveying a higher level idea. What the function is actually saying is "return true if the user has access to the following product".

So the function should look something like:

can_use_product? product
Tags: ruby

Testing File operations 03-24-2011

I've recently been working on a gem that will integrate git and pivotal into my current command-line workflow. I'll talk more about that in a future post, but check it out if you're interested. As I've been working on it, I have become increasingly aware how awesome mocking and stubbing are. I've been using mocha(gem install mocha #bros) for all of my needs and after a little playing around it has made me a very happy person. I haven't had much use for either until this gem I've been working on. The gem does more file operations that I normally do since most web stuff is heavier on the db action.

On this project I ran into an issue where I wasn't sure how to test the following code.

def load_project_id
  File.open('.git/config') do |file| 
    file.each_line do |line| 
      if line.slice('[pivotal]')
        return file.gets.tr("\s\t\n",'').split(' = ').last

For this chunk of code, I wanted to spoof the variable 'file' so that I could make sure that everything in the File.open block does what it needs to. At first I thought that there might be a way to stub the variable that comes in to the block, but it ends up there is a more straight forward thing to do. I ended up turning File.open(".git/config") into File.open(git_config) where git_config is a method that determines the git config directory based on the current working directory. This way I can test this method by stubbing the git_config method with some file I've put in the /tmp directory and keep my config files clean.

Dot-Rspec files 03-02-2011

I was recently working on a small library for assigning people a schedule and I decided to go with rspec 2 for testing. As I was working with it, I found that you can use a .rspec file to keep all of the settings in which seemed like a good idea to me. I'm used to having config files like that what with .bashrc, .rvmrc, etc. My file was laid out as such:

--format documentation

I could then run the command rspec spec/libs/* and it would run all of my tests in the desired format. I didn't want to have to specify the directory every time and so I decided to add the -I option in my .rspec file to include the directory. This, for some reason, would not work and while looking for a solution, I found the rspec 1 to 2 upgrade page with my answer.

Create a Rake Task

Under rake task it lists how you can set the options using a Rakefile, which in retrospec(...har), I should have been using anyways. I ended up using something like the following:

require 'rspec/core/rake_task'
RSpec::Core::RakeTask.new do |t|
    t.rspec_opts = ["--color", "--format documentation", "--fail-fast"]
    t.pattern = ['spec/libs/*.rb']

Now I can call my tests with rake spec.

Moral of the Story

Don't use .rspec for your rspec configurations. You'll probably end up needing a Rakefile at some point anyways so you might as well use that.

Tags: rspec ruby

Magic Ruby 2011 02-13-2011

The Talks

Nothing speaks to people like the word 'free'. It is a good reason to attend Barcamps. And while Magic Ruby is free, that is not the only reason I went (though it made it hard not to). I've been developing in Ruby for a little over a year and I'm still amazed at what a good community it has.

I enjoyed all of the talks, though the keynotes were definitely the highlights. Probably because they involved relatively little code detail, focusing on concepts and kept the momentum going. I think that one of the most difficult things to do is give a speech and have it involve a good deal of code but still not be too dry. Also, the talk length was around an hour each, which means that the speakers have to maintain the audience's attention that entire time. Not a small task.

Lightning Talks

For anyone who hasn't given a lightning talk it is somewhat of a shocking experience(har) if you have to prerecord them. For Magic Ruby, they had you record your slides prior to giving the talk using Jink , then during the talk the slides change without your prompting. So if you time things wrong, you can potentially end up with ten or twenty seconds to kill before you can move on to the next topic. I just used that time to complement my audience.

I ended up giving a lightning talk on a tool I've been using more and more over the past year, Pivotal Tracker.

Git Hooks + Pivotal Trackers

In my development environment I had been taking advantage of their API. It lets you do just about anything you can do from their site, only from the command-line. Seriously, if you're not using it, stop what you're doing and make an account. End of plug. Ok, so I had been using a script in my git hooks that pulls in the current stories that I'm working on and prepends them to my commit message so that it is easy to associate a commit with the ticket that you're working on. In my personal time, I've been working on a gem that uses this idea. I hope to have it finished in time for the Orlando Barcamp.