RubyFlow : The Ruby Community Blog

Home   Submit   Sign Up   Log In   leaders   Twitter   RSS Feed  

nixterrimus — 7 posts

I recently posted a pair of VIM tips for working more quickly with Rails projects.

The first tip speeds up ctrl-p for large rails by ignoring directories you don't want to autocomplete. This fixes a HUGE annoyance in large projects where the file you want sometimes isn't even in the list.

The second tip speeds up searching insides files for rails projects.
One of the patterns I've been using when building restful APIs is creating a model for collections. This model then uses a factory method for instantiating from a set of params. I've found this cleans up controllers significantly and creates a nice place for tests to hang off of. I've written a blog post about this building complex collections from params pattern.
I wrote a blog post about Rails API performance tuning about tools that I find useful and some common performance problems.
I've been using Vagrant, a tool for creating instant development environments quite a bit recently. I've written a blog post to Introduce Rails developers to vagrant.
Ever accidentally commit some code, push it, and then find out that there were failing specs? Use a pre-commit-hook to avoid this pain, I wrote up a tutorial on Using pre commit hooks to run your specs
Over the weekend I came across a piece of code that had a $. variable in it. I was intruiged and spent an enjoyable hour playing with global variables. Ruby has quite a few cryptic dollar variables and I've written about them and attempted to demonstrate using many of them in Cryptic Dollar Variables & Their Meanings in Ruby
I recently needed to track user behavior to allow them to update resources but didn't want them to have to create an account. To accomplish this I built a visitor class and used cancan to manage permissions. I've written a short writeup about Managing Resource Ownership Without Creating an Explicit User Account