HandicapPrinciple (ThoughtStorms)

Compare : MarketForLemons

[Zahavi's http://octavia.zoology.washington.edu/handicap/handicap_principle.html Zahavi's handicap principle] offers an explanation of the peacock's tail in evolutionary theory. Because longer tails are unweildy, having one is a handicap to the peacock which has it. For this reason, only very fit peacocks can afford the cost of the longest.

I'm starting to realize that the handicap principle is the enemy of the rational attempt to avoid effort I call RadicalLaziness. I'm starting to see the handicap principle at work wherever I find a commitment to unnecessary effort.

For example :

** Maybe compare AdSense ClickFraud (http://www.blogmaverick.com/entry/1234000470073786/))

"because use of Java and the extra effort it requires is a filter which removes all but the cleverest and most hardworking programmers."

Perhaps, although I think this is an argument used more by the programmers themselves than the companies that employ them, who are instead taken in by "professional" industry opinions about the suitability of languages. A lot of Java advocates claim that other languages don't enforce rigid design processes et al, which the companies pick up on without necessarily worrying about the actual quality of work, just that which is perceived at the end of the day.

I'm also not sure that companies intentionally make their sites horrible to use. I think this comes down more to a misunderstanding of the platform, in a world where style is queen. Companies used to tailoring all their content - adverts, press releases, etc - towards making a good impression (as is encouraged by a capitalist lilt?), rather than considering its practicality values. The people in charge of such projects have a tendency to think of it as a promotional product that shows off the company, rather than as a useable service. "Never attribute to malice what one can attribute to stupidity." Maybe this is the same thing, just along a different track (i.e. presentation as a form of handicap).

Not arguing per se, just putting a different spin on it... :)


Interesting article by JoelSpolsky points out the virtues of putting good C++ programmers writing Visual Basic. (The http://www.joelonsoftware.com/articles/fog0000000006.html) The) winning situation for those companies doomed to write Java because of the handicap principle is to use a mixed language model. A modicum of JavaLanguage to establish macho systems programming credentials (and even filter out lousy programmers) and do the real work in a scripting language.

Could GroovyLanguage be the scripting language Java shops are dying for?

: Instead the academic is signalling her fitness through parading an unfeasably large bibliography

Odd. That's never been my view of why citations are deemed so important.

Citations are important in academia because your worth in the community is judged by how important your work is, how often it's cited, etc. In many ways academia is an instance of TheAttentionEconomy.

A long citation list isn't proving your fitness, its improving others'. Not citing properly is a sin because (in the context of the academic community) it's theft. Citation is the GoogleJuice of the academic community.

-- AdrianHoward

Of course! This page should be connected to LinkingVsCiting

-- PhilJones

Contrast :