-
Website
http://willwilkinson.net/flybottle -
Original page
http://www.willwilkinson.net/flybottle/2004/12/29/contractarian-functionalism-posnerblogging-take-two/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Robert S. Porter
56 comments · 1 points
-
uknowbetter
362 comments · 19 points
-
huadpe
40 comments · 1 points
-
Vangel
72 comments · 1 points
-
Michael Drake
110 comments · 3 points
-
-
Popular Threads
-
A Little Mystic Nationalism
3 days ago · 41 comments
-
Scott Winship on Income Inequality
2 weeks ago · 26 comments
-
Now Let Us Praise Results-Facilitating Virtue!
1 week ago · 8 comments
-
Why Are There So few Women in Philosophy?
2 weeks ago · 20 comments
-
Hey, I Can’t Actually Quite Imagine a World in Which Things Are Exactly as Different as the Need to Be to Give Me What I Want, but It Would Be Neat if I Could!!
2 weeks ago · 21 comments
-
A Little Mystic Nationalism
1) Desirable to whom is not a silly question, or certainly wouldn't have been thought silly by the Spartans, for example. And different social orders might be desirable for different circumstances, war, famine, the need for very rapid development.
2) Sparta may provide an example of another problem, in that once norms and prejudices are instilled, they can be hard to change when external circumstances change.
Just because some social conventions are irrational or groundless, they can still be valid in that they provide the consensual regularities that support the order.
Thomas Jefferson wrote the 'design document' for America and then the Founding Fathers hammered out the 'code'. There were some obvious flaws in the original code, America 1.0, slavery and limited sufferage for instance, but they didn't crash the program. In fact, the original program was put together so well, it's still in use 200+ years later.
When there was enough 'users' to request a 'feature change', women who wanted to vote, for example, the 'code' was updated.
The level of abstraction needed to create an original program, when a country is founded, requires the skills of polital philosphers, equivilant to a software architect. Architects tend to make poor coders, because they worry too much in the abstract.
I think this is Posner's point. Subsequent changes to the code don't require such high level thought. It only requires a large number of people wanting the change, and a fairly low level coder to make the change in a way that doesn't change other users experience in a negative way.
Speaking of which, where exactly are the large numbers of 'users' calling for a change in Social Security?
The analogy is pretty good, as far as it goes. It does tend to pit demographic cohorts against one another, and makes no allowance for social or philosophical progress.