The Number One Trait of a Great Developer
tammersaleh.com
The Number One Trait of a Great Developer
1–10 of 122 posts
Re: The Number One Trait of a Great Developer
#2We embrace complexity at our peril. Dullness is a virtue.
Re: The Number One Trait of a Great Developer
#3Re: The Number One Trait of a Great Developer
#4Yes, yes, yes, and thrice more yes. We embrace complexity at our peril. Dullness is a virtue.
It's not as simple as that though - it all depends on the context of the project. Sometimes it is perfectly OK to go crazy and use bleeding edge technology other times that would be daft - it all depends what you are trying to achieve mixed in, as the article says, with a heavy dose of judgement.
Re: The Number One Trait of a Great Developer
#5For example you see a bad thing in the code? If you can understand the problem and the risks and benefits, you can make a good decision. If you can possibly make it better, understanding the time available to you, and the risk to the product, you should make it better. Not put it off and let the bad thing become more entrenched technical debt.
Making that kind of decision, requires good judgement. It requires understanding your own skill, time management, risk, and more.
Being able to exercise good judgement comes with extreme rewards for any project, as there will be less costly mistakes, and more successes and better code.
Re: The Number One Trait of a Great Developer
#6Re: The Number One Trait of a Great Developer
#7This is an old story, but I guess it has to be retold every few years, to inform newer developers and to remind older developers (and management).
Re: The Number One Trait of a Great Developer
#8Re: The Number One Trait of a Great Developer
#9Re: The Number One Trait of a Great Developer
#10Maybe it's just because the post is out of date now (2011) but I'm not sure why "new technology", "rockstar" and "produces unmaintainable code" are all conflated together.