David Black

Lookin' on Up...To the East Side

I am currently reading the Well-Grounded Rubyist by David Black. It is a great book and reading it reminds me of things I was confused on when I started in Ruby. One of those things was the path Ruby uses to figure out which method to call when inheritance and mixins are in play.

As I read it last night, I thought I should post about it, so here it goes. Let’s start with a simple class.

Conferencia Rails 2009

The Spanish community Rails conference (aka Conferencia Rails) is so close! Last week we opened the register (what are you waiting for?), late than usual, but this year everything is a little bit more messy, because this year the conference is growing in a lot of aspects:

Lookin' on Up...To the East Side

In which I provide an enormous amount of examples to explain Ruby’s method lookup path.

I am currently reading the Well-Grounded Rubyist by David Black. It is a great book and reading it reminds me of things I was confused on when I started in Ruby. One of those things was the path Ruby uses to figure out which method to call when inheritance and mixins are in play.

As I read it last night, I thought I should post about it, so here it goes. Let’s start with a simple class.

Interview: Author David Black

Our Book Promotion: “The Well-Grounded Rubyist” starts today. Win one of four books to be given out for active participation. The coolest thing? Author David A. Black will be on site to answer questions! Click here for more details. Here, in this brief interview, Satish Talim of RubyLearning talks to David A. Black.

Book Promotion: The Well-Grounded Rubyist

Book Promotion: The Well-Grounded Rubyist

RubyLearning is pleased to announce the promotion of the book “The Well-Grounded Rubyist” by author David Black.

The Well-Grounded Rubyist

training by the greatest ever team of ruby ninja pirate ringmaster factotum samurai accountant programmers ever known to man or woman

Hello all.  I can't believe I haven't blogged about this yet, but David Black (author of some of the best Ruby books out there), Rick Olson (Rails core.  The technoweenie.  Need I say more?), and myself are conducting some Ruby training in Atlanta on April 1-3, 2009.

The ultimate ruby training

Over at @entp we teamed up with David Black, old school rubyist, trainer and mentor to collaborate on a training session. If you’ve been sniffing around Ruby or Rails and want to get a solid foundation, this is the session for you. If you work with people you’d like to truly understand idiomatic ruby, or just want to convert them to the one true way, this is where you should point your boss: http://entp.com/training/ The sessions will also be taught by Jeremy McAnally, who needs no introduction around here, and Rick Olson will be on hand to help take things to the next level.

Revisiting Python

I used to be an avid Pythonista. I poured over Python books, read huge swathes of Python code (including the source of Twisted, which, as its name might imply, I think of as quite a personal accomplishment), and soaked up as much material as I could find. I had survived the relative chaos of Perl, and was relieved to find a more orderly, seemingly sane language to work with. I dove in, and I loved it.

Notes from the Ruby Manor (part 2)

So this is Ruby Manor part 2. After the Ruby Manor morning session we had a tasty pub lunch, rocked up a little late, and settled down to an interesting afternoon of Ruby talks…

Again, the errors and omissions are mine.

Jonathan Conway – Neo4J

In the beginning we had flat files. They worked well. Then we got relational databases. Great for ad-hoc queries and they allow you to define relational constraints. Brilliant. However, there are problems…

Notes from the Ruby Manor

I’m lucky enough to be at RubyManor today; a Ruby conference organised by Ruby users, for Ruby users, costing the grand total of twelve of your British pounds. A bargain, as you’ll see if you check the lineup of talks and speakers.

I started making notes, but it seems to have evolved into some kind of blog post. Apologies for typos, crap grammar and glaring errors.

Syndicate content