Ruby Kaigi 2010 Day 2

Holy crap am I tired. It's been a long awesome day. It started out with some excitement:
  • Just found out I have an hour time slot when all I prepared was 30 minutes. Ok, time to write some more. #rubykaigi
  • Panic! Maybe I'll talk about metric_fu a bit. #rubykaigi
I must have looked at that schedule 20 times and never realized that I had an hour slot. Everyone else had 30 minutes so I thought I did too.
  • Attendees of "The Importance and Implementation of Speedy Tests" will also get "Metrics Based Refactoring" at no additional cost! #rubykaigi
I did something I almost never do: Look at crisis as an opportunity (crisi-tunity). I had to write "Metrics Based Refactoring" anyway for Windy City Rails so why not write it now. In less than 4 hours. While watching my friends present at a conference. Looking over those sentences now I can't believe I didn't freak out.
  • Ted Han used publicly available data to settle reviewing bais accusations against "The Edge" of hating the PS3 #rubykaigi
  • Turns out there was no bais. Math to the rescue! #rubykaigi
  • bais? bias? baise? no idea.
You are probably not surprised to find out that I can't spell. Even Eito Katagiri, who did a wonderful job translating my slides, found a bunch of spelling errors and English is not his first language.
  • I just pulled out a table in the main hall and the table police where all over me. My mistake. Sorry. #rubykaigi
There were announcements everywhere about not doing this and yet I did. In my defense: I'm an idiot.
  • They're giving out an award to the person who committed most to Ruby 1.9.2: Yusuke Endoh #rubykaigi
A very nice gesture. Lots of class here at Ruby Kaigi.

Time for Matz's keynote!

  • Matz is talking about Ruby 2.0... again. #rubykaigi
This topic is a staple of Matz's speaking career. I think the first time I saw him talk, years ago, he was talking about Ruby 2.0. Someday...

  • "Right now ruby is just good enough" - Matz #rubykaigi
  • Matz hates local variable propagation (the lack thereof) but no one else seems to care so he's abandoning it. #rubykaigi
  • Ruby's private is not private: it can be accessed from subclasses and overridden by accident #rubykaigi
  • Monkey patching modifies the class globally. #rubykaigi
  • Classbox is the solution to global monkey patching #rubykaigi
Lots of talk about the mysterious 'classbox.' What is it? Well here's a paper on the subject:

And some pertinent lines from the abstract:
...Unfortunately existing approaches suffer from various limitations. Either class extensions have a global impact, with possibly negative effects for unexpected clients, or they have a purely local impact, with neg- ative results for collaborating clients. Furthermore, conflicting class extensions are either disallowed, or resolved by linearization, with consequent negative effects. To solve these problems we present classboxes, a module system for object-oriented lan- guages that provides for method addition and replacement. Moreover, the changes made by a classbox are only visible to that classbox (or classboxes that import it), a feature we call local rebinding. To validate the model we have implemented it in the Squeak Smalltalk environment, and performed benchmarks.
Now for more Ruby 2.0 preview:
  • 5/2 => 2 should be 2.5 or 5/2 (rational) #rubykaigi
  • Inheritance in ruby is more for connivence than for other merits #rubykaigi
  • Matz is thinking about moving mix-ins to a traits like solution which would have conflict detection (unintentional overrides) #rubykaigi
  • You could declare the 'mix' and specify how to deal with conflicting methods. #rubykaigi
  • mix Foo, [:*] would copy all constants from the mix, or you can specify which ones you want and rename them #rubykaigi
  • mix raises error on method/constant name conflict or removing #rubykaigi
  • From Matz's slides "Ruby 2.0, just started, small step from 1.9, should be done soon" #rubykaigi
  • Ruby 2.0: Traits, Classbox, Keyword arguments, a few other nifty features #rubykaigi
  • There some fierce discussion going on in IRC about the proposed changes in Ruby 2.0 #rubykaigi
The debate on 'mixes' got pretty hot and heavy. Keep in mind that all this IRC chatter is displayed behind Matz while he was giving his keynote because the translations are done in IRC. So you'd be reading a translation of what he said right along with people discussing it.
  • My presentation on "Speedy Tests" and "Metrics Based Refactoring" starts at 13:30 (10 min) in room 200 #rubykaigi
  • The 'slides' from my presentation on "Speedy Tests" http://is.gd/eHNTN #rubykaigi
I think the talk went very well. Especially considering that I wrote the second half fairly fast.
  • I just disparaged integration tests in favor of unit tests. Next up is @p_elliott talking about how he only does integration #rubykaigi
  • .@p_elliott does a lot of things to make his integration test fly. I would like to see one of their suites. I could learn a lot. #rubykaigi
So I asked Paul how long their suites take and he said that they develop on 8 core machines and use Specjour to utilize 4 more cores so they tend to run between 5-8 minutes. Pretty damn fast for full stack integration testing.
  • Hey, someone else made the 30 minutes vs. 60 minutes mistake. I feel better now. #rubykaigi
Except he found out at the end of his presentation when he asked: "How much time do I have left?" and go the response: "25 minutes." Yipes. Luckily there were a lot of questions.
  • .@nusco did a really good job explaining the basics of Ruby metaprograming
  • RT @sudhindraRao Whatever works in #java does not work in #ruby. Even huge classes are maintainable. @rubykaigi
  • .@nusco's favorite metaprogramming trick is method_missing. I thought he was kidding but he was not. #rubykaigi
When he said method_missing I grabbed the microphone back and responded: "Really?" I couldn't help myself. I tend to avoid method_missing. There's usually a way to do what you want with other programming tricks.
  • Modules are extremely decoupled and can be tested in isolation so they are very flexible @nusco #rubykaigi
Good point.

  • Lightning Talks! I'm excited! #rubykaigi
Talking very fast does not lend itself to translation. But still they were very cool. Even better there was a lady in a kimono who would 'gong' you if you ran out of time.



The gong lady stikes

That is awesome.

After the lightning talks a few of us went back to the hotel to drop our things of before the party and we ran smack into this huge festival that happens once a year in Tsukuba. Here are some pics:




Festival 11

Festival 4


Festival 6

The party was super nice. And they had a fantastic spread of wonderful foods and drinks.

Comments

Post a Comment

Popular posts from this blog

What's a Good Flog Score?

I've been using Flog to measure the complexity of my Ruby code and I was wondering how others interpret Flog numbers. I'll go first with my opinions: Score of Means 0-10 Awesome 11-20 Good enough 21-40 Might need refactoring 41-60 Possible to justify 61-100 Danger 100-200 Whoop, whoop, whoop 200 + Someone please think of the children (note: these are scores for an individual method) The 20 - 60 range is interesting to me. Sometimes the complexity of what you're doing will justify the score and other times the method is in desperate need of refactoring. The highest Flog score I've seen in the wild was in the 300's. What's you're personal high and what do you think of my rankings? In other news, I've redesigned the look of my blog so if you only see my post through a reader you might want to stop on by, take a look, and tell me what you think.
Read more

SICP Wasn’t Written for You

The number of software luminaries who sing the praises of “ Structure and Interpretation of Computer Programs ” (referred to as SICP) is such a long list that you might think only a crazy person would take issue with it. However, to ignore SICP’s problems and continue to blindly recommend it seems just as crazy. SICP was the textbook for MIT’s introductory programming class and was a bit of a departure from other into to computer science textbooks at the time.  Wikipedia sums it up nicely:  “Before SICP, the introductory courses were almost always filled with learning the details of some programming language, while SICP focuses on finding general patterns from specific problems and building software tools that embody each pattern.”  Which sounds awesome, but does essentially say that abstract principles will be introduced before the nuts and bolts of a language.  If you think about that for a minute, you may see where the problems will be. When I was training to be a teacher I took a b
Read more

Point Inside a Polygon in Ruby

Recently my team needed to find out if a point was inside a given polygon and, as usual, we found some code on the internet that did what we wanted. And, as usual, there wasn't much explanation as to what it was doing. Here's the code (after we converted it to Ruby): 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 def contains_point? (point) c = false i = -1 j = self .size - 1 while (i += 1 ) < self .size if (( self [i].y <= point.y && point.y < self [j].y) || ( self [j].y <= point.y && point.y < self [i].y)) if (point.x < ( self [j].x - self [i].x) * (point.y - self [i].y) / ( self [j].y - self [i].y) + self [i].x) c = !c end end j = i end return c end end So, you know, it works and I'm grateful to somebody for posting it but we had no idea how it works. So we wrapped 2 tests around it (one where the point is not in the polygon and another where it is
Read more