The Number One Trait of a Great Developer
engineyard.com
The Number One Trait of a Great Developer
1–10 of 72 posts
Re: The Number One Trait of a Great Developer
#2Seems a bit pigeon-holey to me. I'd think twice before applying such broad stereotypes.
Re: The Number One Trait of a Great Developer
#3I agree wholeheartedly with this concept. I previously used the term "instincts", but I think "judgement" is better. A solution is more than a technical implementation: it should address the actual requirements of the product as well as the characteristics of the maintainers. A combination of familiarity + ease of development + enough scalability.
Re: The Number One Trait of a Great Developer
#4When I look around at other companies hiring Ruby on Rails developers, I see them focusing on three major traits: Super-smart; Large community following; Deep Ruby knowledge.
I definitely agree with the thrust of the article, but I run community sites and have run Ruby job ads for a few years and I can't recall seeing anyone looking for a hire with a "large community following."
In aggregate, across all the listings I've run, companies are most usually looking for experience, team working skills, familiarity with Agile practices, TDD experience and, sadly, the ability to commute to a certain location.
Re: The Number One Trait of a Great Developer
#5[deleted]
Re: The Number One Trait of a Great Developer
#6This essay seems to beg the question. A "good" developer, by its definition, is the who picks the most reasonable, easy to maintain technology, because she knows anything "much more complex would be beyond her current skill." Yet, if she is lacking in skill, how can we be sure her judgment is sound on what a "reasonable" and "easy" technology is? Doesn't the basis for that judgment require superstar-like experience and curiosity?
Re: The Number One Trait of a Great Developer
#7This essay seems to beg the question. A "good" developer, by its definition, is the who picks the most reasonable, easy to maintain technology, because she knows anything "much more complex would be beyond her current skill." Yet, if she is lacking in skill, how can we be sure her judgment is sound on what a "reasonable" and "easy" technology is? Doesn't the basis for that judgment require superstar-like experience a…
[deleted]
Re: The Number One Trait of a Great Developer
#8When I look around at other companies hiring Ruby on Rails developers, I see them focusing on three major traits: Super-smart; Large community following; Deep Ruby knowledge. I definitely agree with the thrust of the article, but I run community sites and have run Ruby job ads for a few years and I can't recall seeing anyone looking for a hire with a "large community following." In aggregate, across all the listings…
I can't recall seeing anyone looking for a hire with a "large community following."
companies are most usually looking for ... team working skills
I believe there is an operating assumption here that active membership and following in a given community is a solid indicator that the individual in question has very good team interaction skills, as well as working knowledge of the community's domain focus.
Re: The Number One Trait of a Great Developer
#9This essay seems to beg the question. A "good" developer, by its definition, is the who picks the most reasonable, easy to maintain technology, because she knows anything "much more complex would be beyond her current skill." Yet, if she is lacking in skill, how can we be sure her judgment is sound on what a "reasonable" and "easy" technology is? Doesn't the basis for that judgment require superstar-like experience a…
Developers who lack skill are awful at picking technologies. I like to think of it like this: when the guys that don't know anything start picking the tools they are basically throwing darts at a board. Everything is going to seem random. Sure, some of their picks will be correct, but most are going to be awful selections that make maintaining the project a very unpleasant experience.
Re: The Number One Trait of a Great Developer
#10This essay seems to beg the question. A "good" developer, by its definition, is the who picks the most reasonable, easy to maintain technology, because she knows anything "much more complex would be beyond her current skill." Yet, if she is lacking in skill, how can we be sure her judgment is sound on what a "reasonable" and "easy" technology is? Doesn't the basis for that judgment require superstar-like experience a…
I would say that once you reach a certain level you are able to determine which technology is reasonable based on things like language familiarity, community support, and documentation.