Gregory Brown ( @seacreature ). In a past life, I was a professional technical ...
Issue #8: Uses for Modules (1 of 4) 2011-04-13 18:00, written by Gregory Brown Originally published as part of the Practicing Ruby newsletter on December 8, 2010. Most of these issues draw inspiration from discussions and teaching sessions at my free online school, Ruby Mendicant Univ...
When using inheritance like this you are wasting resources (a class in this case) and so far I see only one advantage: changing the constructor is a bit easier because the old implementation is available via super without having to resort to alias or reimplementing member initializati...
Practicing Ruby's second volume now freely available 2012-03-26 14:00, written by Gregory Brown Keeping with my promise to release content from my Practicing Ruby journal , I’ve put together a massive link dump of articles from its second volume. Please enjoy them and share them with ...
If you haven’t watched Jim’s talk yet, I’ll remind you to go ahead and do that now. But assuming for some reason you can’t or won’t, you should know that the kinds of complexity that connascence can be used to reason about typically have something to do with coupling. The relationship...
Today, we’ll focus on the question that caused me to write this series in the first place. Many readers were confused by my use of extend self within earlier Practicing Ruby articles, and this lead to a number of interesting questions on the mailing list at the time these articles wer...
Issue #21: How to practice (1 of 2) 2011-09-06 16:00, written by Gregory Brown Originally published as part of the first volume of the Practicing Ruby newsletter on January 22, 2011. Most of these issues draw inspiration from discussions and teaching sessions at my free online school,...
USP: Implementing signal handlers - some caveats 2012-03-27 00:25, written by Eric Wong Signal handlers may run at any time If your program receives a signal, Ruby will invoke the associated signal handler as soon as it is able to. This means a signal handler can hijack your existing ...
This is a reasonable question to ask, because this approach is just as straightforward and has similar strengths and weaknesses. If Ruby did not have an open class system, you could argue that it’s less likely that you’d run into side effects with different definitions of SimpleLogger...
