I used to play role playing games in High School. Namely, the Teenage Mutant Ninja Turtles Role Playing game. I was the GM. I played almost every weekend with my brother and my best friend–the center of the football team. I loved those games. I think we ignored half the rules, but the stories we created are still some of my best memories from that time.
Take a look at this email and think about what it would mean about your career.
What about this email is different than most of the job postings out there that you routinely see?
I’ve been running a few tech interviews for the consulting company that I get work from and I’m realizing, most people aren’t very good at it.
But that’s understandable. It’s not like we do it very often and it’s hard to get practice in on the interviewee side (interviewers do this all the time). Here are a couple of mistakes I’ve seen recently:
When talking about interviews, most programmers are interested in the technical interview. And why not? It’s what we know. We think that if we can solve a problem on a whiteboard, we should get the job. Meritocracy for the win!
When my Dad got out of the Army in 1971, he got a job with AT&T as a repairman. He worked there his whole career for 41 years until he retired two years ago. This was normal for his generation and the generation before his. You got a job at a big corporation right out of college (or the Army) and they took care of you, treated you like one of the family and carried you through your career to a safe, and funded, retirement.
With the latest news that Reddit, of all places, is now forcing all of its employees to move to San Francisco to work in their local office, or go find a new job, I again thank my lucky stars that I have the option to work remotely. It’s a great time we live in when all of the tools we need and all the collaboration we want can happen anywhere in the world at any time.
I was browsing Quora recently and came across a question called What are the best kept secrets of great programmers?. These kinds of questions always make me cringe a little. Everyone’s always looking for secrets and shortcuts and the simple fact is, there aren’t any. There’s never just one thing that people-who-get-stuff-done know that no one else can’t figure out.
The dreaded technical interview. The bane of any programmer that’s not sure of themselves. I’ll admit to being nervous in every interview I’ve ever been in, even though I’ve gotten an offer nine times out of ten. (I’m very good in an interview).
The call came in around 3:00 PM and I ran outside to take it in private. The call was from the start-up in Michigan that I had been interviewing with for three weeks and they had finally made a decision.