Polymorphic Rants

While I was reviewing this (awful) code, I realized how an enum for me is nothing more than a strategy pattern out of the box in Java.

Few days later I read this interesting article from Ralph Johnson (GoF anyone ?) where he says something pretty close to my point of view:

Design patterns are not made of stone.
[...]
Over time, we should change our programming languages so that they build in things that used to be patterns.

If Ralph and I are on the same page, I’m happy

This evolution of modern languages will (hopefully) increase the number of people that are really able to write Object Oriented code, thinking about behaviour and not just about data.

Just in case you were waiting this feature as much as me…but Google is progressively adding IMAP support to  GMail

Here the announce on the GMail blog.

The fifth edition of the Agile Day has been announced.

As usual it’s an incredible opportunity to talk with a lot fo smart people of everything is related to agile methodologies; either if you are an experienced agile pratictioner or you are just starting knowing this world this is an appointment you can’t miss !!

If you write something along the line of that:

public enum MyError {
ERROR1, ERROR2, ERROR3;
public static String explain(MyError code) {
switch (code) {
case ERROR1:
return "message for the error 1";
case ERROR2:
return "message for error 2";
default:
return "generic error"; }
}
}
You seriously don’t have a clue of what Object Oriented is.

p.s. yes, this is real code I’ve recently seen (thanks God not from any colleagues…)

Saturday (October, 20th) the Italian JavaDay conference will be in Turin.

The occasion is pretty interesting to listen and talk about hot topics in the Java World with the speakers and all the attendees 
Check it out !