Also, the lack of future bugs and lack of future difficulty in expanding and adapting good code may result in a lack of attention for that code (people may not appreciate its subtlety and elegance and merely think it solves an easy problem to start with).
The end result may be that the developer takes longer to resolve fewer bugs and implement fewer bits of functionality than other developers while the benefits of higher quality design and code might be largely invisible.
Discerning developers may be able to recognize and appreciate higher quality coders, but in environments with short-sighted or overly bureaucratic management I'm sure this sort of problem exists.
Another difference is that a basketball game has a definite, qualitative outcome. That, at least, can be measured. With software development you don't even have that luxury.
Which is why software development is still very much a craft. And a pretty esoteric one at that. It often takes the subjective judgment of a known good developer to determine the quality of another developer's contribution. The unfortunate side effect of this is that the really good dev shops (populated by talented devs even in management roles) are working at levels many, many orders of magnitude beyond what the run of the mill dev shops are capable of. There are a great many development projects managed or overseen by non-developers, and many of those people lack the basic skills necessary to tell the difference between gold and utter crap. It's no surprise then that so much "enterprise-y" development is little more than snake oil, VBA scripts and MS access duct taped together and sold for millions of dollars to big companies who don't have the skills to know they got taken for a ride.
Software development is only just barely scratching its way out of its alchemy and astrology phase. There are far more untalented, unskilled hacks out there than there are honest craftsmen.
http://blogs.msdn.com/larryosterman/archive/2004/04/20/11699...
I was just wondering if there were parallels for this in programming.
The obvious might be the various approaches and "methodologies" to programmer or team productivity based on dubious or non-existent hard data.
But I'm more wondering if there are tools or techniques that don't get any accolades (like, say, MVC or TDD or the framework of the week) but have a peculiar synergistic effect that ends up providing significant (and possibly counterintuitive) value.
What's the "Shane Battier" of software development practices?
And how would you know?