You'll love Woods' Edge at Salt Creek Golf Retreat, Brown County, Indiana.
Coder v. Developer
This is a great discussion of the value of experienced coders. Check it out if you write code for a living, or are considering doing so.
he was making a distinction between being a coder and a developer, a distinction made very well by Mike Gunderloy in his excellent book, Coder to Developer. Mr. Gunderloy differentiates a coder — someone who understands the syntax and semantics of one or even a number of computer programming languages – from a developer — someone who can turn out a full application with all the required supporting details.
If I was a COBOL-coding drone who just translated detailed specs into executable code, I recognize that I could easily be replaced by someone willing to work for a whole lot less. But, reading the column, it was obvious that Mr. Adamsky was talking about both coders and developers. I quote:
There’s little future for someone who only programs. Code is a commodity that can be created by other people for less money – much less. Think of coding as the beginning of a career – a great place to start, but not what you want to do for your entire professional existence.
…
I firmly believe that much of bad software comes from a lack of imagination over how software might be used in ways different than those we anticipate. While our industry should not underestimate the value of a newly minted computer science graduate’s enthusiasm, it should also not underestimate the value of a somewhat less enthusiastic, but seasoned, interested and experienced coder.
http://myopiczeal.blogsome.com/2005/03/15/coder-v-developer/trackback/
