3 ms·

Funny anecdote: I was recently contracting at a company that was OOP gone amuck. Everything written in Java ca. 2001 style. Lot's of message wrapping and unwrap

by troels 11y ago

Funny anecdote: I was recently contracting at a company that was OOP gone amuck. Everything written in Java ca. 2001 style. Lot's of message wrapping and unwrapping. Lots of dependency injection fun and games. At some point, their lead developer tells me about some guy they had for a job interview a while back, and as the story goes they had him through a code review where he was berated for using a static helper class. Apparently his reply was something like "You're using static classes for view helpers? But that's insane!". The morale of the story as told, was that clearly he didn't know right from wrong and was passed over. I didn't know what to reply to that.

arethuza 11y ago
"Java ca. 2001 style" also seemed to include using every feature of J2EE even if it wasn't remotely relevant. Crazy files of constants seemed to feature a lot as well: public final static string HTTP = "HTTP"; public final static string COLON = ":"; public final static string SLASH = "/"; and then the inevitable: string url = HTTP + COLON + SLASH + SLASH....; [I did think about posting it to the DailyWTF at the time but thought that might be bad form when you are the lone contractor trying to rescue the project.]