You may think of live coding as a necessary evil: the thing you have to resort to when a connection fails and you can't get at a running example, ...
Link: dablog.rubypal.com
You may think of live coding as a necessary evil: the thing you have to resort to when a connection fails and you can’t get at a running example, or when someone asks a question you’re not sure of the answer to and you have to try it out in real time. Admittedly, memories of coding in...
Splitting hairs over "resource": the case for the affirmative (Part 2) April 24th, 2008 In part 1 of this two-part post, I explained my concern that the word “resource” has become too closely associated in Rails-related usage with some combination of model, database table, and control...
Splitting hairs over "resource": the case for the affirmative (Part 1) March 22nd, 2008 I’ve commented on the main Rails mailing list and elsewhere about some concerns I have about the way the term “resource” has been adopted into Rails practice and discussions. I’d like to explain th...
In Ruby, you can write methods whose names end in ! (exclamation point or “bang”). There’s a lot of confusion surrounding the matter of when, and why, you would want to do so. What ! does (and does not) mean The ! in method names that end with ! means, “This method is dangerous”—or, m...
I’ve recently found myself describing single objects yielded by iterators as “magic pens.” Though it may sound more psychodelic than technical, it’s actually proven to be a good way to explain these objects and give people a feel for why an iterator would only yield one object in the ...
Meta, shmeta: learning Ruby horizontally January 7th, 2007 One of the great accomplishments of Ruby is that its object and class model bring about a wonderful unity and simplicity. Even things that might seem like they should be hard or obscure are actually very transparent, once you ...
