I am looking for an intern (more details) for later this year. I have a number of interesting ideas for projects, most of them involve Ruby (more specific JRuby), Android and Eclipse. Your skill set should include at least Java and if possible Ruby and/or Eclipse API.

I’m looking for a commitment of at least three months (I would prefer six) and you should be within one or two years of receiving degree. If this sounds interesting please apply here and add a note that you would like to work with Frank Spychalski in Munich.

Yesterday was Girl’s day and our office hosted a few girls from schools in and around Munich. Read the rest of this entry »

I found the DIY page for demotivators and had to create one for Ruby. Enjoy!

Second day has started. Today it starts with a few talks on testing…

George Malamidis — „Synthesized Testing“

Already 15min behind schedule, but so far interesting.

This has 4 lines of code. It is already a big ruby function.

Vassilis Rizopoulos — „rutema: One test tool to rule them all“

I’m thinking on how to write in a polite way “This talk was boring”. It was. And the tool uses XML Hey, this is a Ruby conference- you should use YAML or even better a cool Ruby DSL.

Tomasz Stachewicz — „Sharing the load“

Sounded interesting but there was a question after the talk which suggested that the guys reinvented the wheel and that BackgroundDrb is a better solution for what he has done.

Petr Krontorád — „Building Rails Playground - using Ruby’s dynamic nature“

Mumble, mumble, small text, cannot read the slides, mumble… Sorry I don’t have a clue what this talk is about.

Tim Becker — „Lessons Learned Writing Native Extensions“

Type-along tutorial on how to write C extension for Ruby. Very interesting, this could actually make me write C code again… He has started talking on cats and tigers and it seems like he wants to teach us how arrays work in C. Booooooooring. Finally he is done with this and is back on the interesting topics like conversion of data types. Overall a really interesting talk. By far the best one today so far. Tim’s post with code samples and links.

Matt Ford — „Aspect Oriented Programming in Ruby“

It’s his birthday. Happy birthday Matt! He talks about Aquarium a neat aspect oriented programming solution for Ruby. Very nice. I have to play around with this when I’m back home.

Dushan Wegner — „Philosophy & Programming“

This first lightning talk. “Imagine I’m holding a beer and put out this ideas”. “Programmers are better philosophers”. A very cool talk about the similarities of programming and practicing philosophy.

Marcin Raczkowski — „Distributed programming with ruby“

Hard to understand but interesting. Sadly it is impossible to read his code when he is showing examples in the editor.

sorry missed name and title Akira Tanaka - „IO.copy_stream“

Interesting talk about IO in Ruby. Great final “status” slide:

Accepted by Matz yesterday @La fabrica
Submitted today to Ruby 1.9

Wow!

Gregor … — „Context-oriented programming for Ruby“

Took a long time to get to the point. Which part of lightning talk did you not understand.

Florian Gilcher — „Patterns (yet another) pattern matching library“

Interesting talk. Can be found at patterns.rubyforge.org.

Raimonds Simanovskis — „Using Ruby with Oracle“

Good quick talk. I never had to work with Oracle so I never had the problems he was talking about.

Daniel Liszka — „One RubyStack to Rule them All“

Strong accent, to much text on the slides. But sounds like a neat idea… www.bitnami.org/stack/rubystack

Ry Dahl — „Ebb Web Server“

Yet another Ruby web server, obviously it’s faster than all the others because what would be the point otherwise. ebb.rubyforge.org

Wouter de Bie — „Capistrano, Webistrano“

The final lightning talk. I’m hungry off to find some food…

Dr Nic — Demo

So it wasn’t the last talk. They squeezed in a short demo on how to use his gem generator. Very cool! I have to use this to play around with native C extensions.

Final announcement

It seems like next year’s EURUKO will be in Madrid. Great! Never been there. See you next year! It’s not decided yet. Krakow and Warsaw are possible sites, too. Hm, I’m still for Madrid

Sumary

I think I should have slept in today like Todd and would not have missed a bit. Here are some pictures from EURUKO 2008 on Flickr and even one with me. EURUKO was great. A big “thank you!” to all the people who have organized it. I’m sure I will be back next year, no matter where.

The first day of EURUKO 2008 is over.

Yukihiro „Matz“ Matsumoto — „Keynote“

Matz talked about the future of Ruby. It was very interesting. He talked a little bit about the upcoming features (I will link to the slides when they become available) and about the design decisions behind Ruby. For me the most important quote was:

I designed Ruby not to work best but so that people can perform best

Koichi Sasada — „Ruby meets VM“

Koichi explained some details of YARV but some points were lost because a few of his slides were in Japanese.

Favorite quote:

(on his “No Ruby/No Life shirt”) for me it’s No Ruby / No Job

Charles Nutter and Thomas Enebo — „JRuby: Ready For Action!“

Made me download JRuby during the talk

David A. Black — „Per-Object Behavior in Ruby“

I have to reread the slides, because I fell asleep (not due to the talk but to the fact that we are in Prague and had a few beer yesterday)

Nic Williams — „Meta-Meta-Programming with Ruby“

Memorable talk, very funny, great final slide (see @16:35)

Lightning talks session

Two talks on an agile white board and on a Ruby to PHP compiler.

VC with DHH

a little boring, bad sound quality and even worse video

I just found out about EURUKO 2008. It will take plaze in Prague, Czech Republic, on March 29th to 30th. From what I’ve heard are EURUKOs fun events and I would like to go this year if I can find the time especially because of this announcement:

19. 02. 2008 · Matz is coming to EURUKO!
We are very happy to announce that Matz (most probably accompanied by Koichi) is coming to EURUKO! There are currently more than 100 people registered to attend, so thank you all! We will update the website in next couple of days with more details on program, information about sponsors and other stuff.

It has been some time since I used Ruby but it is still my favorite language by far.

Update:

I just registered for EURUKO I will probably go by car so if someone from the Munich area needs a ride, just leave a comment… And a bonus feature: I found this Tech Talk of Matz talking about Ruby 1.9 today…

Today I tried to run JRuby on Android. I failed. This article is more like a lab report so expect more boring details… Read the rest of this entry »

As you can see I’m toying around with the android SDK. I guess this will be my first 20 percent project here at Google.

So far I’m impressed with the state of the SDK. There is a ton of documentation and up to now everything worked at once.

I have a couple of ideas I would like to try on android but unfortunately all of them involve bluetooth and there is no bluetooth support for the emulator (yet?).

If you have a great idea you would like to see as an app for your next cellphone, just leave me a comment or implement it on your own

• Turn on computer
• search for google tech talks at video.google
• turn up the volume and start working

ps: I watched Seattle Conference on Scalability: Lessons In Building Scalable Systems, an older talk called A New Way to look at Networking and Haiku: The Operating System

I recently bought Beautiful Code. In chapter 7 Alberto Savoia writes the essay “Beautiful Tests” about the use of randomized tests to easily create a wide range of inputs for a system under test.

I really like and use his idea of randomized tests. But there is one very important hint missing in the chapter:

Initialize the random number generator for every test to a fixed seed!

Why? Tests should be repeatable! Otherwise you can never be sure if you have fixed a bug from the previous test run, because you don’t know if the same test data was created.

Why for every test? Again: tests should be repeatable! If you want to run a single test and the random number generator was initialized for the whole test suite, you behavior will change for all but the very first test case.