raganwald
Tuesday, September 20, 2005
  Spot the Bug and Interviews Gone Wrong
Spot the (Java) Bug:

private final static long THIRTY_DAYS_IN_MILLISECONDS = 30 * 24 * 60 * 60 * 1000;

...

final Date today = new Date();
final Date thirtyDaysHence = new Date(today.getTime() +
THIRTY_DAYS_IN_MILLISECONDS);

Sheesh.

I promise that if I ever ask someone to spot this bug in an interview, they can gather their resume, code samples, and references up and walk out without another word.

More about interviews gone wrong: Nah'mean? and Other Interview Stories

Where does one begin with those stories? Obviously, interviewing and recruiting is a two-way process. If the interviewers are superficial, you can bet the company will be superficial. Is that what you want?

On the other hand, some people have an idea of propriety that does not strongly correlate with their fitness as employers. In other words, they might expect you to dress conservatively and be polite for an interview, but that doesn't mean they won't be great people to work with/for.

The whole dress code and manners thing boils down to something quite simple: when meeting new people in a business context, your dress and mannerisms should not call attention to themselves. This works both ways: I own custom tailored suits and a full set of 'tails', but few of my software development colleagues have ever seen them :-)

I'm not advocating some sort of herd mentality. I'm suggesting that you want your accomplishments and potential to stand out. I'm all for making a huge personal impression, but let it be about your talent, not your gear.

Think of your clothes and manners as a windowpane. Sure, you can present some interesting stained glass. But won't that obscure all the interesting things about you?

p.s. Reg blows an interview

Labels:

 

Comments on “Spot the Bug and Interviews Gone Wrong:
Test
 
Ah... I actually had to write a test case. Pesky things, integer literals. ;)
 




<< Home
Reg Braithwaite


Recent Writing
Homoiconic

Share
rewrite_rails / andand / unfold.rb / string_to_proc.rb / dsl_and_let.rb / comprehension.rb / lazy_lists.rb

Beauty
IS-STRICTLY-EQUIVALENT-TO-A / Spaghetti-Western Coding / Golf is a good program spoiled / Programming conventions as signals / Not all functions should be object methods

The Not So Big Software Design / Writing programs for people to read / Why Why Functional Programming Matters Matters / But Y would I want to do a thing like this?

Work
The single most important thing you must do to improve your programming career / The Naïve Approach to Hiring People / No Disrespect / Take control of your interview / Three tips for getting a job through a recruiter / My favourite interview question

Management
Exception Handling in Software Development / What if powerful languages and idioms only work for small teams? / Bricks / Which theory fits the evidence? / Still failing, still learning / What I’ve learned from failure

Notation
The unary ampersand in Ruby / (1..100).inject(&:+) / The challenge of teaching yourself a programming language / The significance of the meta-circular interpreter / Block-Structured Javascript / Haskell, Ruby and Infinity / Closures and Higher-Order Functions

Opinion
Why Apple is more expensive than Amazon / Why we are the biggest obstacles to our own growth / Is software the documentation of business process mistakes? / We have lost control of the apparatus / What I’ve Learned From Sales I, II, III

Whimsey
The Narcissism of Small Code Differences / Billy Martin’s Technique for Managing his Manager / Three stories about The Tao / Programming Language Stories / Why You Need a Degree to Work For BigCo

History
06/04 / 07/04 / 08/04 / 09/04 / 10/04 / 11/04 / 12/04 / 01/05 / 02/05 / 03/05 / 04/05 / 06/05 / 07/05 / 08/05 / 09/05 / 10/05 / 11/05 / 01/06 / 02/06 / 03/06 / 04/06 / 05/06 / 06/06 / 07/06 / 08/06 / 09/06 / 10/06 / 11/06 / 12/06 / 01/07 / 02/07 / 03/07 / 04/07 / 05/07 / 06/07 / 07/07 / 08/07 / 09/07 / 10/07 / 11/07 / 12/07 / 01/08 / 02/08 / 03/08 / 04/08 / 05/08 / 06/08 / 07/08 /