The Results Oriented Developer
In the process of reading about technology job recruiting, I came across alot of writing about what keeps good programmers from leaving their jobs. While doing all this reading I came to the realization that I do not need a “programmer”, I needed an “Application Developer”, and alot of attributes that some ascribe to the “best programmers”, are attributes that I do not think make a very good “Application Developer”. What I really need are “Results Oriented Developers”, and here is a list of qualities that make them so (at least in my mind).
What makes a “Results Oriented Developer” ( in no particular order):
- They work with customers directly, not through a project manager. If the developer cannot see and hear the customers pain, then they are too insulated.
- They understand that the code they write today could be crap six months from now when the specifications change drastically.
- They do not need to work in a crypt of silence. They exist, if not thrive, on the chaos that is the real workplace.
- They favor completion of a project and customer satisfaction over code style.
- They use the tools they have to do the job. They do not use the tools they have as an excuse. (you do not need Photoshop 8 to design a website, and you do not need 2GB of RAM to run MS Office)
- They find humor (and job security) in last minute spec changes.
- They do not cop a condescending tone if a coworker does not use some obscure object naming convention.
- They are comfortable working in 2-3 development environments, and/or projects, every day.
- They are self-managing to the extent that if a customer calls with a small change, the developer can balance the need for customer service, and meeting deadlines.
- They understand the humor behind me having a red stapler on my desk.
March 9th, 2009 at 3:18 pm
I saw your blog while searching Google. Very interesing article I must say. I will now share it with my facebook friends.