One of my primary frustrations is dealing with web developers that don't know anything about how a web server actually works. They don't understand how the server receives data. I think Charles may be dealing with the same issue. If you are a developer, you should know how to set up your own development environment. If you are a developer, you should know how to set up a project from scratch. If you are a web developer you should know how to set up your own web server. If you are a database developer, you should know how to set up a database. Also, if you are a developer, you should know how to read. I am amazed at the number of questions that I have to answer, simply because my fellow developers don't know how to use Google. Are these requirements to much to ask from a fellow coworker? I am getting to the point where I am not sure I want to hire anyone unless they are actively developing in their spare time.
Posted by carl at May 20, 2003 12:58 AM
Hiring people who actively develop in their spare time should always be the goal. As a rule, these are the people who not only know what they are doing but are capable of finding out what they don't know. And when this is the case, they can generally get themselves up to speed rapidly, because they are practiced at it.
I've never understood the motivations of programmers who don't like programming.
Posted by: Cameron at May 20, 2003 03:36 AM
A colleague of mine once remarked that we shouldn't hire programmers that don't have their own Web sites.
I have long been wary of programmers that didn't own a computer and I guess this is an update to that.
Maybe one day we won't hire them unless they have a blog. :-)
Posted by: Darren at May 21, 2003 11:38 AM
Comments