• Entry by Youri Bonnaffé
• Usage: mvn exec:java

No, code is to be written in English. You can't read English, you can't code (or at least you'll miss most of the resources available out there).

I don't think so and by the way you said that the live coding at Devoxx will probably be in Java, so I guess I picked the right language (and the one I know the most too...). Main advantage is that most of the developers can read Java so it is just simpler. I might write a Groovy version to see how it compares, especially since the exercise is well suited for a scripting language.

At least you understand the project structure, tests are where you expect them to be.

Navigation in packages on Github is so painful so this is just a way of simplifying it. Yeah, yeah on real life I'll put real package names.

YAGNI, KISS, blahblah. Just to print something String works too.

No state, no needs for objects

That's what I tried, but TDD by the book (going as far as running the tests with compilation errors) just feels slow, especially on simple problems that can fit in your head. Since I had examples and precise specifications, I started by writing them as acceptance tests. Then I wrote the code, made the tests pass and wrote more tests.

Isn't working code awesome?

Actually coding the exercise felt a bid sad and not that compelling mostly because I was doing it on my own. I'm eager to join you guys to work on some code! And yes I'm willing to do it in the eden space pool!