59 karma · joined June 3, 2013
When I interview candidates, I look for a good foundation for what they will be working with like do they know the difference between class and struct and the implications of using them (day 1 kind of stuff).
Then I ask them about how they would go about solving a problem they were unfamiliar with. Google-foo is a skill that must be learned and honed. I don't care if you can spit off all sorts of acronyms, I want to know if you are capable of using common sense to solve a problem.
Last but not least, how do they stay up-to-date and relevant. Not looking for the 8 to 5 developers and not interested in those cutting-edge guys either.
Must have good understanding of the basics, principals and skills in problem solving. Telling a block of code that you have a masters in CS will NOT make the bug go away.
This was just what I needed to break the stress of my day.
I dislike the title "Senior" when discussing developers because it's usually just a title given to those who have 1) been there there at least 3 years or 2) Have n years of development related experience on their resume. The problem is, the title is associated with level of assumed expertise. As the article says, these guys can barely answer a basic question.
However, that's not to say that they don't know how to be productive or produce quality results.
It wouldn't be so bad if developers just went out and read someone else's code or attended a code camp or user group, but they don't.
While recruiters tend to generalize requirements, they aren't looking for generalists. They're looking for candidates that match specific keywords.
I get letters from them for Drupal contracts, when the C# to Drupal ratio is 500:1 on my resume.
Unfortunately, the tech world has made us "our f-ing khakis".
What are the performance implications of having this gem running on a page?
I'll be sharing this with my twitter followers.