Really love the latest path update. Messaging was the missing piece. Thanks @path at Leetchi – Read on Path.


The 24th was the release of the long awaited version 2.0.0 of Ruby. It’s now time to start using it.

Start by making sure you’re running the latest version of rvm: rvm get head

Ruby 2.0.0 deprecated syck in favor of psych so you will need to install the libyaml using brew or any other package manager you like: brew install libyaml

You also need to make sure that openssl is installed: rvm pkg install openssl

Then last but not least: rvm install 2.0.0 --with-openssl-dir=$HOME/.rvm/usr --verify-downloads 1

You’re all set. Start using it now by running: rvm use ruby-2.0.0

Enjoy.
GL


I’ve recently came across the Mailbox iPhone app and it triggered on of my recent thoughts: “We don’t need email labels anymore”. Let me explain in details.

First let’s see what’s a label. The label is only a mental mark. It’s like a tag or a folder if you want a real life equivalent. So when you need to search for a specific email you’re going to look into that label/folder and start searching for it. It feels a bit painful and even if it feel natural thanks to the identical use of papers and folders that we do every day, it can be improved.

Now let’s take a look at google’s gmail search. It’s so accurate that you don’t really need this mental hassle. The search engine will index everything there is to know about your emails in a much better way that simple labels. It will search the inside and out of your emails so you don’t need the labels anymore.

That’s why as of today I will remove all the labels from my GMail account and use search exclusively to go throughout my email. It feels simpler and much faster.

GL


Foo Fighters - These Days (by foofightersVEVO)


If you’re like me and you do a lot of deployments every days on your staging or production environements, you might end up wasting a lot of time waiting for your application to be built.

After some digging it looked like the asset pre-compilation was taking most of that time (between 150s and 350s) and since I don’t work on those assets on every deploy I don’t need to precompile them every time.

But don’t be afraid there is a solution to it. It’s as simple as a gem. The gem is called turbo-sprockets-rails3 and thanks to Nathan Broadbent there is also a buildpack available for heroku.

So all it takes to speed up your deploys is o install that gem:

group :assets do
  gem 'turbo-sprockets-rails3'
end

Then bundle it.

To use the Heroku buildpack all you need to do is create a new app using it:

heroku create --buildpack https://github.com/ndbroadbent/heroku-buildpack-turbo-sprockets.git

Or add it to your existing app:

heroku config:add BUILDPACK_URL=https://github.com/ndbroadbent/heroku-buildpack-turbo-sprockets.git

That’s it you’re done. The first build might be a bit long since it will precompile every assets but the following ones will be lightning fast.

Enjoy.

GL