- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Hey, if you call someone for an interview with a half hour notice, taht's waht you get.
Admin
Admin
I got halfway through the first story and thought "shoot, now mine will never get published, that's way too similar". The changes were just enough to put me off. It was mostly intact though, but with swearing removed and orange tan added. Edit: Unless there's another Ray Smith, I was also misattributed for the 2nd submission too. I blame Steve.
Admin
Zimbabwean dollars don't count.
Admin
Not true. I was a consultant for about 10 years, each day making several hundred $ a day (with consultancy fees increases every year).
I only wore suits during interviews, and only one consulting gig (back in 2001) required me to wear long sleeves and slacks (no jeans except on casual Fridays.)
There are some lucrative consulting gigs where we must use a suit - meeting executives, having top-notch skills in in some niche tech areas where you get called because no one else in house can fix some shit that is broken and is bleeding the company a ton of money.
FOR THAT, I can see the argument. But there are a lot of consulting gigs that can EASILY pay $268/day (the equivalent of $70K) just for starters without requiring a suit.
The average consultancy work is certainly above $300/day. People making $400-500 (or even more) while wearing jeans is not unheard off.
On another note, the last time I was required to wear a tie was from 1995 to 1998 (my first full-time software job), and it was as an employee, not a consultant.
Having said that, I have to agree with you in my bewilderment with the herds (not hordes, but herds) of unwashed geeks who seem allergic to the notion of using a suit.
Grow the hell up people. Anyone short of being a singularity of ugliness looks good and professional with a suit. And you don't work in a suit, you simply wear it to meet customers. Then you take it off, you roll your sleeves, unfasten the belt and the tie a little and you get to work.
And for those of you who insist in coming to work with sandals, by God, clip those toenails and remove whatever sandy, mold-ridden green/gray bacterial mat that is underneath them.
The rest of us normal humans with a sense of hygiene can see that crap a mile a way. Clean that crap, you don't need it for programming.
Admin
Just for sake of nitpicking, you DO IMPLEMENT interfaces in abstract classes. They probably asked why you extend interface in another interface, not in abstract class.
Admin
ANSWER>>Full!<<ANSWER
Admin
I was on the giving end of an interview which could have gone this way. As it happens, these applicants didn't know the answers as the primary criterion was whether they would work for 1/2 my rate or less. Since I disdained to give them the answers, my recommendation was no-hire to all, and also to get a better recruiting firm. Naturally, my replacement was hired over my objections. Last time I checked, the company's stock was in the toilet after a severe service level agreement-impacting production issue.
Admin
Actually a first timer
Admin
says who?
Admin
Uhm, if you try to write 'abstract class extends <interface name>' you will get an error as a class cannot extend an interface. A simple test with a javac will show you so. Or reading jls. An abstract class implementing an interface need not implement any method however.
Admin
"(like why you need to extend an interface in an abstract class declaration instead of implement)"
This is wrong, you implement an interface in an abstract class in the same way you would a regular class, the only difference if you don't actually have to implement the methods, that can be left down to the concrete implementation..
Admin
The third story reminds me a lot of my latest job interview.
I just finished my studies at the University (business informatics) and was eager to find a job, to finally earn some money. I sent a few job applications to a few companies and had a pretty good hit rate of getting job interviews.
Knowing that job interviews are my weak point, I prepared very thoroughly for every one of them. Reading about the company and what they do, reading about job interviews in general, preparing questions that I can ask, and so on.
Since I was applying for a software developer/administrator kind of position, I also looked at some programs that people where required to code during interviews (like fizzbuzz).
The interviews I had where pretty much the standard procedure. Nothing out of the ordinary. But one job interview stood out to be pretty... interesting.
I arrived on time, was greeted very warmly, got offered something to drink ("Coffe? Tea? Water?"). Then the interview began.
First question: "Do you know what we do?"
Luckily, the interviewer then got someone from the IT to join the interview. I expected to answer some questions myself now. But the IT guy only told me some stuff about what they do there.
Conclusion: I spent about 20 minutes on this interview. It was ME who was asking all the questions. In the end, I got a job offer (which I accepted, btw). But it was a very strange job interview nevertheless...