Capycoder: Chrome Extension to Record Interactions as Capybara


Seriously why hasn’t anyone ever told me about this awesome tool?

With CapyCoder (below) you can literally record you interactions with code and the tool will write Capybara tests as you click.

I found that I couldn’t exactly move the recordings completely unedited into my capybara suite (for example, CapyCoder will create a visit path that goes to your dev site, which won’t work in a Capybara test suite), but with a little editing they worked splendidly.

Capycorder Chrome Extension

Programming Resource for Cutting Edge CSS/JavaScript Developers

Here’s a great resources for CSS & JavaScript developers who want to be on the bleeding edge of CSS3 and HTML. Interactive visualizations show you browser support for various parts of the language you want to try out.


Goldiloader: “Just In Time” Eager Loading Gem for ActiveRecord

Typically to eager load in Rails you use the .includes(:xyz) method in the controller code (or wherever you are making the search call)

Here’s an interesting solution that does “just in time” loading based on how the view will render, eliminating the need to put includes into your AR queries.

Haven’t use it but it looks pretty cool.


CanCan evolved to CanCanCan

So apparently ryanb/cancan has evolved to CanCanCommunity/cancancan

#rails #authorization #gem


How do I name my Rails associations if there are multiple relationships to the same class object?

Here’s some advice I gave on the Rails-talk list this morning. (Information specific to the question I was answering has been stripped away to make this more of a general-purpose answer.)

You probably read that the rails default is to use the class name as the association name. In the case of multiple associations to the same classes – possibly through join tables – this is actually a confusing way to name your associations.

Consider something that is not your data model: An “Article” that has both an Author (user object) and an Editor (user object)

The standard way to write your association is like so:

class Article < ActiveRecord::Base
  belongs_to :user

But the problem here is that you actually want two relationships to two different user objects (one for author and another for editor).

As you have already discovered, you can use a different name for the association name, as long as you pass class_name as an option to your association declaration, like so:

class Article < ActiveRecord::Base
  belongs_to :author, class_name: “User”
  belongs_to :editor, class_name: “User”

In the example above, your Article table would have a foreign key for author and editor (my personal naming convention is to name these author_user_id and editor_user_id, that way the field conveys both the relationship itself and the class that it relates to).

The is a really, really good idea because the worst thing in an app is to have a relationship to a user_id and as the future developer be scratching your head wondering if the original developer intended that to be a “editor” or an “author”. I strongly recommend using this style of naming convention when you will have multiple relationships to the same classes, as you have in the example below (a user’s relationship to a billing can be either as a creditor or as a debtor).

Remember, the association name you give is for you (& Rails) to identify that association elsewhere in your codebase. Although the default is to use the name of the foreign class, it is by no means required.

Data modelling is actually a lost art. But as a general rule of thumb for beginners, you should avoid duplicitous relationships (also known as circular dependancies).

Note that if one relationship describes a “creditor” (user) and the second one describes a “debtor” (user), that doesn’t actually count as duplicitous (for the purpose of my argument). It would be duplicitous if a foreign key describes the same relationship already described in another place (like a different foreign key or through a join table). That’s what you want to avoid.

I love creating old-fashioned ERD (Entity Relationship Diagram) on a napkin. Also you might want to learn a little bit about the ancient art of “3rd Normal Form”.


Learning Git

Here’s a good online tutorial for learning GIT

Online tool to publish Word Documents to HTML

Although Word has a built-in “Export to HTML” feature, it has a host of problems that produce less than ideal markup for your website. For one, it is extremely verbose and secondly it has specific problems exporting unicode characters correctly.

As an alternative, you can use this online tool, which outputs nice clean HTML for you to use in your markup. It even has a host of options, including removing empty paragraphs, converting <b> to <strong>, <i> to <em>, replace non-ascii with HTML entities, and replacing smart quotes with ascii equivalents. Very useful.