Given the number of people alive, and the number of research positions in universities, I have trouble accepting that this premise was ever true.
1,032 karma · joined March 28, 2007
I love to code. :D
10 PRINT "BASIC LIVES AGAIN!!"
20 GOTO 10At that point, you won't have to face the dilemma of doing the right thing vs. making rent.
Yes, especially if he's giving stock tips from the future. ;)
There's no sense in having your customers have to wait through a chain of three companies (counting yours) before their support tickets get resolved.
... and you get compensated in experience. ;)
Yeesh. I already misread the headline; this just reinforces it. :(
Karma? ;)
$ man ispellBecause they do matter. The function of any level or style of dress at an interview is to mark you as part of the Right Group. This holds true even when the interviewers don't realize that they're unconsciously doing it.
Overdressing for an interview at some companies can put you in the Wrong Group just as surely as underdressing will at others.
That explains everything.
I had a friend who actually got turned down for a management position for wearing a suit to an interview (they thought he was "too formal" for the job). PayPal, I believe.
I rock the Silicon Valley Casual for interviews-- jeans and an untucked button-down shirt for consulting gigs (and employee-jobs that I already know I want).
If it's a really creamy consulting gig for a large company, I might even make it slacks, semi-dress shoes, and untucked button down. Regrettably I don't have the complexion for khakis, since blue button-down, brown semi-dress shoes and khaki slacks [with cell phone on a belt clip] appears to be the uniform of choice around here large boring companies that think they're casual.
For startup interviews, I will wear a funny t-shirt, often involving pirates.
You will note that I never overdress beyond these levels (for an interview), as the casual dress is part of my filter against stupid, boring companies.
My only question is why do the robots carry cash?
Which in turn should remind you of RoboTron.
You might have had some exposure to the subject, but probably as part of other problems, i.e. not under the name Computational Geometry. For me, the most valuable thing was learning that this was an actual field with a name, which gave me a starting point for self-study.
Also check out Computational Geometry in C, Second Ed., by O'Rourke. It goes into more low-level implementation details (the first book I mentioned is a good high-level introduction to reasoning about geometric algorithms, so you should read that first).
I suddenly feel the need for much, much more RAM...
Probably can't tell you how we solve it at work, but the very much publicly-available book Computational Geometry: Algorithms and Applications, Third Edition by de Berg, Cheong, et al., mentions something about the robustness of geometric algorithms using inexact (floating point) vs. exact arithmetic. :-)
WWZD?
Let us all learn to be responsible adults, like Generation X!
Workaholic instant-noodle-eating late-nighters occasionally need reminders of upcoming calendar events.
Take that, iPhone!