By raganwald
via fishdujour.typepad.com
Published: Nov 30 2007 / 16:32
I found this interesting. The author agrees that Singleton isn't that relevant in practice, but it is a very well-known pattern, so he seems to be using that as a springboard for drilling down into issues like initialization options, visibility choices, thread safety, performance, and so forth.
Comments
FlySwat replied ago:
Yet another interviewer who thinks that solving a whiteboarded code problem indicates developer knowledge.
amalter replied ago:
I'm sorry flyswat, but what possibly does indicate developer knowledge besides solving development problems?
I cringe at the number of candidates that have walked through my door talking a good game of this architecture or that design pattern, but couldn't code the simplest problem.
It's not a trivia contest, it is a way to start a conversation. The same type of conversation that I want to have with the person day in and day out as part of their job.
Ryan Ginstrom replied ago:
By using a Singleton implementation to interview candidates, he kind of proves the point of his post. Thus, vote up :)
dzonelurker replied ago:
"I think the Singleton is pretty much irrelevant in these days of Dependency Injection".
True, Singleton is overrated. OTOH Spring DI is based on Singletons!
nightwind replied ago:
Not being able to solve a simple problem on a whiteboard or being unable to have a meaningful discussion about should be an automatic "no hire". It is for me, at least. Good post.
Voters For This Link (17)
Voters Against This Link (3)