Buzzwords
July 29th, 2005
I just stumbled on this article (people reading this blog, will understand why these things jump to my eye). I was quite amazed by the Jared's opinion:
- on spring:
Give brownie points on keywords like IoC, DI, etc. etc.
- on design problems:
Here, buzzwords like Singleton, encapsulation etc. will fly out anywhere and if the candidate really knows what he/she's talking about, smile.
Usually, when I hear people spawning buzzwords, my bullshit-o-meter goes all the way into the red. The fact that a candidate has read the spring homepage, doesn't tell me much about this experience with the framework. Of course, keeping score like this is a very handy trick for hiring managers who are a bit uncertain about the technical domain they're interviewing about.
I'm afraid I wouldn't pass Jared's interview. My reaction to buzzwords is to avoid them. Moreover, some of his concerns (Have you ever used a Singleton!) come so naturally to me, that I wouldn't even consider it to be a "design achievement".
I'm afraid interviewing is an art, not a list of questions.
Via Erik.
April 21st, 2008 at 10:18 PM Buzzwords are good and bad for us. Sometimes it's utterly abused, misused by unscrupulous people. And sometimes we as developers use them to communicate effectively at each other(Tell me what's a shorter word for Abstract Factory Method or Command Pattern? ;)) instead of explaining a lengthy description of each we use it like a secret handshake. On the other hand, you'll know who has just read a Spring website and someone who actually used it even if they try to make out a story of their past projects the obvious will still show. Anyway, thanks for a special post about this. ;)