Pat Shaughnessy’s “Using a Ruby Class to Write Functional Code” gives an example of bringing functional programming principles into object-oriented design. I like it.
Ruby on Rails models tend to grow and grow. When refactoring scopes, it turns out you can move them into their own classes.
While adding a big feature to PCO Check-Ins, I was struck with this way of describing my approach to adding complexity to the system.
To resolve a bug, a developer must know the behavior and the purpose of the program at hand. I’ve been reading Lesslie Newbingin and it made me think of this.
ActionController::Base once, in
ApplicationController, is a great Ruby on Rails practice. However, if
ApplicationController is your only abstract controller, it’s likely to become a maintenance challenge. To avoid this, you should extend
ApplicationController as needed and move as much code as possible into its subclasses.
You can use C code to prepare methods for mruby scripts.
mruby is an implementation of Ruby that’s designed to be lightweight & integrated with C. To get started, you can run a bit of Ruby code from inside C code.
Sadly, PCO is getting out of the batman.js game.
I was just pondering whether a person ought to have children or not. It’s funny when I try to be the judge.
Batman.js is a front-end MVC framework with an unrivaled implementation of key-value observing. I will explore computed properties in batman.js by contrasting them with Ember.js’s computed properties.