Re^2: On Interviewing and Interview Questions

Team player is very important! I've worked on a project where one guy went off for months to work, more or less in secret, on an "interesting" problem, and came up with an "interesting" (but useless) solution - haemorrhaging money in the process. He went away.

Comment on Re^2: On Interviewing and Interview Questions

Replies are listed 'Best First'.
Re^3: On Interviewing and Interview Questions (Beware of a guy in a room) by eyepopslikeamosquito (Archbishop) on Aug 26, 2005 at 11:04 UTC
Yeah, this is what Jim McCarthy calls Beware of a guy in a room (point 6). Curiously, it's usually the most brilliant developer who goes dark. Years ago, the top programmer of a company we were dealing with got away with saying "it will be ready next month" for 18 months without ever allowing anyone to see his code until it was finished! All developers, no matter how brilliant, must make their code available for public review in modest (fortnightly, say) increments. Update: see also: Beware of a guy in a room (youtube)	[reply]
Re^4: On Interviewing and Interview Questions by DrHyde (Prior) on Sep 06, 2005 at 10:29 UTC
That is mostly a failure of management. Be honest now, most programmers would do that if they knew that deadlines and requirements were of no consequence.	[reply]