4 ms·
This passage gives me a good idea: The OPower guy said they had a ton of problems where they will be using Scalding, so I asked him what they are doing
by CamperBob2 11y ago
This passage gives me a good idea:
The OPower guy said they had a ton of problems where they
will be using Scalding, so I asked him what they are
doing in its absence. He said Oh we pojo it. Then he said
pojo this and pojo that, and soon I was drowning in
pojos, so I asked, Sorry, what exactly is a pojo ? Now,
bear in mind I am a Scala programmer and haven't touched
Java in ages, and they knew that. Their whole pitch was
they wanted to inject some new Scala blood into their
tired Java veins, and that's why I interviewed there. So
the guy is agape, and says, you don't know what a pojo is?
When was the last time you wrote Java?
When interviewing a candidate, use some wacky made-up term like "pojo" a lot in offhand conversation, and reject anyone who doesn't ask what it is.
- x0x0 11y agopojo is a common term for java devs, at least any who have been molested by spring
- notduncansmith 11y agoIt's also seen some use in the Javascript community as well (though not nearly as common).
- gkop 11y agoAnd Ruby too (PORO naturally). Leave it to Martin Foweler et al. coin a useful [category of] term[s].
- strathmeyer 11y agoNever heard of spring, never heard of pojo. Specialized in C/C++, STL, Boost, OpenGL and GLUT, GLx... over the decade have only found interviews for Java jobs. Have tried to learn Java, used them a jobs where none of my bosses knew it or cowokers could spend time talking to me about it. Still, I can only get interviews of Java jobs because that is the only work experience on my resume. Why are we all so screwed?
- ExpiredLink 11y agoSpring continued where J2EE had ended in 2006. Spring is the new J2EE. Wherever I can I avoid it and solely use the latest Java EE without dependency to any external bloatware.
- __z 11y agoPOJO stands for "Plain Old Java Object" and it is a somewhat common term. http://en.wikipedia.org/wiki/Plain_Old_Java_Object http://en.wikipedia.org/wiki/Plain_Old_Java_Object The term was coined by Martin Fowler, Rebecca Parsons and Josh MacKenzie in September 2000:[1] "We wondered why people were so against using regular objects in their systems and concluded that it was because simple objects lacked a fancy name. So we gave them one, and it's caught on very nicely."[1]
- ExpiredLink 11y agoFowler ... what did you expect?
- mark-r 11y agoI was once caught out by that tactic. The interviewer asked if I would use such-and-such algorithm to solve their problem, and I said sure, whatever. I was just thinking to myself, give me the job and I'll research it and make it work. It wasn't until much later that I realized the possibility that such-and-such algorithm didn't really exist, and that I had failed the weeding-out question.
- ExpiredLink 11y ago> and reject anyone who doesn't ask what it is Good advice! POJO (not pojo) is a virtually meaningless term. It was invented to denote any class that wasn't derived from a J2EE class (J2EE was superseded by Java EE in 2006 or so). A class with 7 levels of inheritance, implementing 14 interfaces but no J2EE class/interface among them is a "plain" POJO.