Started out teaching English at Embry-Riddle.
Graded 10,000 essays.
Lesson learned.
Became a mathematics teacher.
Discovered computing.
Never looked back.
Location
Houston TX
Education
Stetson University: B.A., M.A. in English; M.S. in mathematics
I actually had a good whiteboarding session in an interview last week. Unlike other, artificial, whiteboarding exercises like you described in your blog article, I was asked to draw out and describe a web services application I had written. Since I drew upon knowledge I had, it was an easy, comfortable, task as compared to annoying exercises like Fibonacci numbers and such.
I absolutely agree with that style of "whiteboarding". I have candidates write some code before the interview (they have a week on the challenge), and then they send it for us to review 24-hours before the final interview. Then, during the interview, I have them make a change or fix a bug in their own code. It works phenomenally well.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Why I don't whiteboard.
I actually had a good whiteboarding session in an interview last week. Unlike other, artificial, whiteboarding exercises like you described in your blog article, I was asked to draw out and describe a web services application I had written. Since I drew upon knowledge I had, it was an easy, comfortable, task as compared to annoying exercises like Fibonacci numbers and such.
I absolutely agree with that style of "whiteboarding". I have candidates write some code before the interview (they have a week on the challenge), and then they send it for us to review 24-hours before the final interview. Then, during the interview, I have them make a change or fix a bug in their own code. It works phenomenally well.