UI Design Pattern Resources#

knitting

I had a great time at Codestock this year.  It wasn’t the pot-smoking, free-loving, mind-altering tribal experience I was afraid of and I didn’t see a single guitar the entire time – though I did talk with one guitar player.

The organizers – Michael Neel, Alan Stevens and Wally McClure -- did a fantastic job and the Knoxville community is quite amazing and enthusiastic.  I also got to meet many people I had previously only known by reputation.

I presented on “The Uses and Abuses of UI Design Patterns” on Saturday afternoon.  I wanted to build out some examples of using a modified MV-VM pattern in WinForms and ASP.NET before publishing the code samples, but wanted to make sure I published out the references from the slide deck.

The point of the references is that while UI design patterns are all plagued by a tendency to have fuzzy boundaries – that is, it can be difficult to compare patterns between different technologies and sometimes can even be difficult to distinguish patterns used in one technology – there is still a paper trail on the Internet that give us clues as to where the design patterns (MVC, MVC Model 2, MVP, SVC, PV, PM, MVVM) came from and how they were originally intended to be used.

In general, the Supervising Controller and Passive View patterns are the best defined, while MVC is perhaps the least well defined.  MV-VM, on the other hand, has some of the best examples on usage – not least because it is so tightly associated with WPF.

1988 - MVC: Journal of Object Oriented Programming Vol 1 Issue 3 http://portal.acm.org/citation.cfm?id=50759&dl=GUIDE&coll=GUIDE&CFID=41635617&CFTOKEN=20661505

1997-99 - MVC Model 2: Java Sun JSP Architecture http://java.sun.com/blueprints/guidelines/designing_enterprise_applications/introduction/application_scenarios/index.html

2004 - MVP: Martin Fowler  http://martinfowler.com/eaaDev/uiArchs.html

2004 - Presenter Model  http://martinfowler.com/eaaDev/PresentationModel.html

2006 - Passive View and Supervising Controller: Martin Fowler http://martinfowler.com/eaaDev/ModelViewPresenter.html

2005-09 – MVVM: John Gossman http://blogs.msdn.com/johngossman/archive/2005/10/08/478683.aspx

MVVM: Josh Smith  http://msdn.microsoft.com/en-us/magazine/dd419663.aspx

An additional resource is this site http://c2.com/cgi/wiki?ModelViewControllerHistory from which we learn that the first MVC pattern can be attributed to Trygve Reenskaug sometime in the 70’s.

Perhaps the most authoritative source for the origins of the MVMV pattern, in turn, comes from the WPF MVVM toolkit (available on Codeplex) where we are told:

Model-View-ViewModel (MVVM) is a derivative of MVC that takes advantage of particular strengths of the Windows Presentation Foundation (WPF) architecture to separate the Model and the View by introducing an abstract layer between them: a “Model of the View,” or ViewModel. The origins of this pattern are obscure, but it probably derives from the Smalltalk ApplicationModel pattern, as does the PresentationModel pattern described by Martin Fowler. It was adapted for WPF use by the Expression team as they developed version 1 of Blend. Without the WPF-specific aspects, the Model-View-ViewModel pattern is identical with PresentationModel.

Posted by James Ashley Sunday, June 28, 2009 6:36:00 PM (Eastern Daylight Time, UTC-04:00) #    Comments [0]
 del.icio.us | DiggThis

 

The Hazards of Love in Atlanta#

On Wednesday, June 3rd, The Decemberists performed at the Tabernacle in Atlanta.  It’s taken me about the intervening two weeks to fully digest it all.

My friend and colleague, Tim Price-Williams, is a big fan of the Tabernacle and drew out a diagram for me and my wife on where to sit and how to get those seats.  First, we needed to arrive two hours before the doors opened at 7.  Then we were to sit outside the left (not the right, or the far right VIP entrance) doors.  As the doors opened, we needed to proceed to the left and up the stairs to the first balcony.  Tim drew a map of the second balcony and then pointed out the four seats he deemed acceptable, just to the left and the right of center stage and flushed against the forward railing.  Wait an hour for the opening band.  Then wait another hour for the main show.

We messed up Tim’s well laid plans from the get go when I forgot to pick up the baby sitter on the way home from work.  After that we were stuck in remarkably heavy traffic and didn’t find parking until about 6 o’clock.  As we waited in line I made a quick trip across the street to pick up a chicken sandwich at Ted’s Montana Grill for dinner.  I’ve been habituated to fast-food chicken sandwiches for years and was pleasantly surprised to find that the basic recipe can indeed be improved upon.  The line started moving at 6:45 so Tamara and I had to eat quickly.

This is where Tim’s advice came in very handy.  He recommended that we each have our tickets in our hands to be scanned – if one of us fell along the way the other could continue on to the prized seats on the balcony.  Everyone else apparently wanted to stand in front of the stage, so we had no problem getting to the second balcony (we didn’t even realize that there was a first balcony above us) and managed to get two seats a row back from the ones we had coveted. 

The opening band was The Blind Pilots (we joked that the were the injured members of Stone Temple Pilots) but it turned out that they were another band from the pacific northwest with an eclectic instrumentation and a folksy/rock feel.  They were really good.  But we were there to hear The Hazards of Love.

The Hazards of Love is a concept album by The Decemberists.  Based on an apparently original Welsh mythology cycle, it was written by lead singer Colin Meloy while in Paris.  It’s received some mixed reviews while the standout songs have been The Rake’s Song and The Wanting Comes in Waves.  Part of the difficulty follows from trying to understand what the songs are about, which is particularly difficult for me since I generally don’t hear lyrics.  Tamara has made some progress in untangling the characters and the events of the songs, however, and during the break between Blind Pilots and The Decemberists she explained quite a bit of it to me.

The Tabernacle, by the way, is a renovated classic movie theater that looks much better with the lights out than with them on.  It is an amazing venue.  The backdrop for the show – gigantic gauze sheets hanging from the ceiling – along with impressive lighting made it even more so.

We didn’t know exactly what to expect since concept albums are typically something done in a studio.  We thought that this would be a modified presentation of some highlights from the album.  Instead it was a full performance of Hazards of Love straight through and faultless.

As the performance progressed, I came to realize that I had fundamentally misunderstood the relationship between the album and the concert.  Normally a concert tour is meant to reproduce an album for fans.  In this case, I slowly realized, the album is just a memento of the concert itself.  I don’t go to that many rock concerts, so it doesn’t mean much when I say it was the best one I’ve seen.  It was, nevertheless, an event that has left a deep impression on me and still stays with me after these weeks.

The core members of The Decemberists were dressed in formal suits for the performance of Hazards.  Shara Warden and Becky Stark, who sing on the album as the Forest Queen and the heroine Margaret, respectively, were dressed in renaissance fair costumes appropriate to the theme.  Shara Warden has the attitude of Joan Jett and the voice of Grace Slick.  Becky Stark was simply ethereal waving her arms about like Elfine Starkadder the whole time.

Again, I have trouble what actually happened during the performance of Hazards itself.  There are large portions of it I can’t even quite remember, and all I have is the strong impression that something amazing occurred.

I do remember that after The Decemberists, Ms. Warden and Ms. Stark finished with Hazards of Love, and after a half-hour intermission, The Decemberists came back out and performed some songs from their previous four albums.  Then Shara Warden and Becky Stark closed the show with a cover of Heart’s “Crazy On You” which I still can’t get out of my head.  For an encore, Colin Meloy constructed a story about the building of the trans-American railway with audience participation while the rest of The Decemberist led a conga-line through the hall.  I also vaguely recall singing Sixteen Military Wives as a round with the floor, the first balcony and the second balcony performing the parts.  The second balcony was clearly the best.

On the drive home I fell into a melancholic mood; I had the sense that some part of me had been sleeping for a long time and that after waking it up I had left it behind at the Tabernacle.  I now find myself replaying The Hazards of Love again and again on my iPod trying to recapture how that lovely night felt.

Posted by James Ashley Thursday, June 18, 2009 12:25:45 AM (Eastern Daylight Time, UTC-04:00) #    Comments [0]
 del.icio.us | DiggThis

 

David Carradine#

kungfu

As with many people, the passing of David Carradine has left me quite shaken.  David Carradine, after all, was the reason I got into consulting in the first place.

Kung Fu, the Ed Spielman TV series in which Mr. Carradine played Kwai Chang Cane, a parapatetic Shaolin monk in the American Old West, left a lasting impression on me.  If you are unfamiliar with the series, it revolved around a half-Chinese half-American man trained in Kung Fu helping people out as he travelled from town to town searching for his American relatives, all the time pursued by the Chinese Emperor's assassins.

It may be hard to believe, but when I found out about the world of Software Consulting, I realized that it was my opportunity to fulfill my childhood dream of living the life of Kwai Chang Cane.  It’s a bit of a stretch, but think about what a consultant does. He travels from company to company assisting them with difficult technical issues they desperately need help to resolve.

Let me say that the reality has been as good as the dream.  In the past year I’ve managed to:

05/08 – 07/08

Upgrade a billing application for a national furniture chain located just off of Jimmy Carter Boulevard from VB6 Forms to an ASP.NET 3.5 application with limited ajax functionality.  In the process, I helped out a group a beleaguered shopkeepers being extorted by local thugs.

08/08 – 09/08

Gather requirements for a POC Silverlight project while investigating why a beautiful roller derby skater was killed.

10/08 – 11/08

Assist in the data migration of an insurance company’s legacy data – horribly denormalized, unindexed and lacking referential integrity – from a Paradox for DOS system to SQL Server 2008.  At the same time I was able to rescue the office manager’s cousin from a Turkish prison where he was incarcerated under trumped up drug trafficking charges.  I was able to do this with some help from friends who are Vietnam vets in hiding from the US government for crimes they didn’t commit.

12/08 – 03/09

Design a reporting framework for a mortgage company going through hard times that heavily leveraged third party charting tools while also arranging a new life for a protected Federal witness -- who was testifying against his mobster brother -- and help him to visit his sick mother before she died.

04/09

This was a fairly quick gig.  I had to design and build a WPF point-of-sale application for a cruise liner.  During installation of the software I teamed up with a consultant from a rival firm to defuse two sophisticated bombs aboard the cruise ship while overcoming our mutual animosity and learning to work together and ultimately develop an abiding respect for one another’s abilities.

05/09

I had some down time in June, so I reminisced about my adventures to my colleagues clip-show style while preparing for a certification exam.

If this makes consulting out to be something glamorous, I want to make it clear that this is not always the case – for instance the time I had to scrub crystal reporting data for a client or the time I had to hunt down oversized alligators in the sewers because they were eating neighborhood pets.  But between those times there can, indeed, be quite a bit of excitement. 

Consulting is definitely not for everyone.  It takes a certain mentality, a certain desire to not have the same routine every day, and of course it never hurts if you have the ability to make plastic explosives out of a matchbox and a stick of spearmint gum or can deploy a multi-tier application with only a command line utility and the spring from a ballpoint pen.

At least I look forward to coming in to work each day knowing that there will be something new and unexpected to make it different from the day before.

And I have David Carradine to thank for setting me on this path.

Posted by James Ashley Friday, June 05, 2009 2:01:36 PM (Eastern Daylight Time, UTC-04:00) #    Comments [2]
 del.icio.us | DiggThis

 

Outsourcing to Sleestak#

sleestak1-349x267

I have a mirror blog called ‘Outsourcing to Sleestak’ that is hosted on my company’s corporate site.  It has seen a recent spike in hits for reasons I do not fully understand.  Looking through the search queries that bring people to my mirror site, I have come to the conclusion that there is a lot of interest in the advantages of outsourcing to sleestak, especially in these difficult financial times. 

As the world’s leading authority on outsourcing to sleestak, I thought it might be helpful if I provide the following FAQ.  Bear in mind that these FAQ are solely the result of my personal research and expertise in the area.  My company has its own outsourcing solution that I will decline to comment on – especially as I am offering a competing solution to the problem of providing cheap alternatives for expensive problems.  So without further ado:

The Outsourcing to Sleestak FAQ

1. Isn’t the plural of ‘sleestak’ in fact ‘sleestaks’?

No.  The plural form of ‘sleestak’ is ‘sleestak’, as in “Ten sleestak can do the work of a typical developer without the added cost of health insurance or the hassle of labor laws.” 

2. I have heard that sleestak are not effective developers and often screw up projects, in part due to their lack of fingers.  Is this true?

This is a common lie spread by jealous outsourcing centers in Bangalore.  While the physical disabilities of sleestak are admittedly problematic, they are more than capable of manipulating polyhedral objects called ‘crystals’.  Work stations in the land of the lost are equipped with large keyboards in which the typical key is replaced with these crystals, making the sleestak more than qualified to search MSDN forums for code samples they can paste into their own projects.  Furthermore, I find these attacks on the digitally impaired to be highly prejudicial and unnecessary.

3. What about the language barrier?

While it is true that the sleestak lack vocal cords, per se, I have never found this to be a deal breaker in working with sleestak outsourcing centers.  Each sleestak ‘tribe’, which is made up of 20 to 30 sleestak, has a ‘leader’ which I like to call the ‘project lead’.  Each leader has a magic crystal around his neck that allows him to communicate in a faux English accent.  Software requirements may be given to the ‘project lead’ who will in turn translate them for the sleestak workforce.  You will never personally have to interact with a sleestak developer.

4. What if I want a project lead onsite at my company?  Is there anyone available to do that?

Besides sleestak workers and sleestak leaders, we also have sleestak from the distant past on staff such as Enik who are highly educated and trained in ‘soft’ skills.  They are experts at telling the client what he wants to hear and will keep the project on track, or at least lead the client to believe that everything is on track.  In a pinch, he is also experienced at rationalizing delivery problems and deflecting blame. 

5. Can sleestak outsourcing meet my advanced programming needs in Silverlight, WPF and other complex technologies?

You are clearly looking at this in the wrong way.  If you are concerned with getting work done, you should look to your internal developers, to independent contractors or consulting firms.  If you are concerned with the bottom line, however, then you need to be outsourcing.  At 99 cents an hour, sleestak are the most cost-effective solution for your programming needs.

6. I think you punted on that last question.  If sleestak don’t know these technologies, then my project will never be completed.  Shouldn’t I be concerned with getting working code, as well as cost savings, at the end of an engagement with sleestak?

Apples and oranges.  It is all a question of motivation.

If you simply want to get work done, then you should give it to an internal team of developers.  Internal developers, however, do not always keep up with the latest technology and methodologies and expect companies to provide expensive training.

An alternative is to hire independent contractors or contractors provided by staffing agencies.  While these are frequently more expensive than internal staff, you can typically be assured of hiring someone with the skills you need to complete a project.  Contractors, however, have the following shortcoming – they dread the day they complete a project because this is the day they must look for a new job.  Consequently, they have a tendency to do only what is requested of them, seeing no need to do additional work that might bring their engagement to an end. Alternatively, they will over-architect a project in such a way that they will be needed well past the completion date for a project since they are the only ones who understand the code.

Another alternative is to engage a high-end consulting firm.  High-end consultants are judged by their consulting companies based on their ability to deliver.  Consequently they will work hard to complete a project as quickly and efficiently as possible in a way that leaves the client happy.  They will juggle development speed, code quality and code maintainability in a manner that best meets the client’s objectives.  Their ultimate goal is to complete a project as successfully and quickly as possible so they can move on to their next project and accomplish the same thing.  The main shortcoming of hiring high-end consultants is that they are really expensive.  They know they are the best and charge accordingly.

If money becomes a problem – let’s be frank, when isn’t it? – and you can’t afford the best solution, then you have a moral obligation to choose the cheapest solution.  Why allow yourself to be straight jacketed by the dictum that you get what you pay for.  With sleestak, you’ll be paying for what you get.

7.  Your answer makes brilliant sense.  But I’ve heard there is alot of turnover among sleestak.  Isn’t this a problem?

Perhaps this is a problem for traditional outsourcing but not for sleestak outsourcing.  Sleestak belong to what is known as a ‘hive mind’.  What one sleestak knows, all other sleestak in the vicinity know equally well.  This basically alleviates all the issues of project hand-over and application maintenance that plague the typical software project.

It is common to call developers ‘resources’.  This gives the impression that all developers are commodities and interchangeable.  Sadly this is not the case, and great effort has to be expended on team building, personality management and motivational techniques.

With sleestak outsourcing, we take these soft issues out of the equation.  The hive mind ensures that sleestak are true development commodities.  If one goes off to join a rival firm or is injured in a freak elevator accident, this is not a problem!  We can replace him with someone with identical skills and an identical knowledge of the project the very next day.

8. I love the idea, but this sounds like science fiction.  How can you afford to bill 99 cents an hour for software development?  Aren’t you exploiting your sleestak?

Certainly not.  Sleestak are not motivated by anything as banal as money.  They are motivated by the desire to achieve client satisfaction – as represented by their client satisfaction target numbers for which they are rewarded with papaya and mangos.  Unsatisfactory target numbers garner a half-hour in direct sunlight, which they find physically painful.  This is a win-win situation for everybody. 

And while there are certainly moral dilemmas involved in the employment of sleestak, this is not your problem.  You can leave the worrying to us.

9. Given the recent backlash against foreign workers, isn’t outsourcing to sleestak a PR nightmare?

Let’s face it.  There’s only one opinion you need to be concerned about – the opinion of your shareholders.  Issues such as community backlash, employee morale, code quality and project deadlines are ultimately peripheral.  The purpose of outsourcing is to demonstrate fiscal responsibility to shareholders.  This is why, when a project goes bad or revenue is lost due to missed release dates, the solution is always to outsource even more work to sleestak – thus demonstrating your ability to quickly respond to revenue loss with efficient cost-cutting.

When it comes down to it, what’s good for sleestak is good for America.

Posted by James Ashley Saturday, May 30, 2009 10:08:26 PM (Eastern Daylight Time, UTC-04:00) #    Comments [0]
 del.icio.us | DiggThis

 

Of Friendship: Lover and Beloved on Twitter#

Boys_King_Arthur_Wyeth

Friendship and the API

We commonly think of an API as merely a set of performative rules that determine how two systems communicate with each other.  An API is also, however, an implicit carrier of a set of semantic rules that dictate how a client application (or, to be more specific, how the programmer of the client application) is to understand these utilitarian instructions. 

A well designed API, consequently, must not only provide all the tools necessary to accomplish certain tasks on the server but must also do so in a way that is easily understood by the client, either by reusing common software metaphors or, more often, by using analogies from the business domain or culture in general to get across the purpose of the API.

In the case of a social networking API, these semantic metaphors must naturally come from common modes of social relationships.  Not surprisingly, this can be a complicated task when the social networking API actually creates new forms of social interaction that are fundamentally unlike the forms we are familiar with.  This is both the promise and, to some extent, the danger of social networking. 

In forging new manners for people to interact with one another social networking technologies also modify and distort the old ways in which people used to interact.  When an office worker prefers to email the person sitting in the cubicle adjacent to hers rather than walk over for a conversation, the nature of the workplace – not necessarily for the worse – has admittedly been changed.

A case of API semantics meaning something other than what they ought to mean can be found in the Twitter API.  In order to form a social relationship with another user, Twitter provides a REST method called friendships/create.

One would assume that, upon calling this method, the current user becomes the friend of the user that is befriended and that a mutual relationship has been created between the two.  This is not the case.  In the Twitter API, friendship is an asymmetrical relationship merely indicating that the person one befriends is a friend to oneself – that is someone that is followed – while one may not necessarily a friend of the person one is following – that is, they have not reciprocated by following back.

This asymmetric relationship is more clear when one considers two additional methods provided by the Twitter API: statuses/friends and statuses/followers.  Calling the statuses/friends method returns a list of people whom one is following.  By calling the statuses/followers method one retrieves a list of people who are one’s followers. 

Rather than a network of friends, the world of Twitter is made up of these two classes of relationships: friends and followers.  Even on the Twitter website itself, one is not provided a means to view all of one’s relationships.  Instead there is one link, “following”, for viewing one’s friends and another, “followers”, for viewing the people who consider you a friend (even if you don’t feel the same way about them).

This is not the standard usage of friendship.  It falls short of Aristotle’s notion that friendship is a reciprocal relationship between two people.

“Now the friendships that have been discussed consist in an equality, since the same things come from both people and they wish for the same things for one another…”  Nicomachean Ethics, tr. Joe Sachs

It falls even further from the mark when one considers Michel de Montaigne reflections on his friendship with Étienne de La Boétie:

“Beyond all my understanding, beyond what I can say about this in particular, there was I know not what inexplicable and fateful force that was the mediator of this union.  We sought each other before we met because of the reports we heard of each other, which had more effect on our affection than such reports would reasonably have; I think it was by some ordinance from heaven.  We embraced each other by out names.  And at our first meeting, which by chance came at a great feast and gathering in the city, we found ourselves so taken with each other, so well acquainted, so bound together, that from that time on nothing was so close to us as each other.”

. . .

“[W]hat we ordinarily call friends and friendships are nothing but acquaintanceships and familiarities formed by some chance or convenience, by means of which our souls are bound to each other.  In the friendship I speak of, our souls mingle and blend with each other so completely that they efface the seam that joined them, and cannot find it again.  If you press me to tell why I loved him, I feel that this cannot be expressed, except by answering: Because it was he, because it was I.”  Of Friendship, tr. Donald Frame

Practices Ancient and Modern

The two parties in a friendship are traditionally a friend and a friend, not a friend and a follower.  And yet the friend/follower dyad isn’t a completely new social relationship, as one might expect from a mode of communication based on novel technology.  Instead it resembles a social structure endemic to ancient Greece in which the participants were called erastes and eromenos, as often as not translated as ‘lover’ and ‘beloved’.  You can find an interesting treatment of the institution, heavily influenced by Michel Foucault’s History of Sexuality, in this Wikipedia entry.

Like the institution of friendships on Twitter, the ancient practice went by the common name for something it was not.  Aristotle expresses concern over this kind of “friendship”, which sometimes went under the code “lovers of friendship”, as he tries to place it within his already overextended catalog of the types of relationships that are possible between two people, which already include friendships of utility, friendships of pleasure and friendships of virtue (true friendship):

“With these [incomplete friends] also, the friendships are most enduring whenever they get the same thing – pleasure for instance – from each other, and moreover, get it from the same source, as witty people do, in contrast to the erotic lover and the boy he loves.

“For the erotic lover and his beloved do not take pleasure in the same things; the lover takes pleasure in seeing his beloved, but the beloved takes pleasure in being courted by his lover.  When the beloved’s bloom is fading, sometimes the friendship fades too; for the lover no longer finds pleasure in seeing his beloved, and the beloved is no longer courted by the lover.”  Nichomachean Ethics, tr. Terrence Irwin

The asymmetry inherent in the “special” friendship between an erastes and his eromenos is due to the fact that they seek different things from each other, and consequently cannot simply be called “friend” and “friend”.  The erastes seeks pleasure from the eromenos whom he follows, while the eromenos allows the relationship to persist because he sees utility in it – he can get something -- whether it be praise or practical gain -- out of the relationship.  The most extreme case of this may have occurred in ancient Sparta (somewhat glossed over in 300) where, because children were taken away from their families at an early age to become soldiers, thus dissolving the familial bond, hereditary titles and political advancement were based on the adoption of youths by their more mature elders into these follower/friend relationships.

The asymmetry in these relationships were also a source for amusement in ancient Athens.  Plato writes about it in the Phaedrus, which is at the same time a dialog on seduction as well as a dialog on the nature of the soul.  The humor inherent in Alcibiades’ party crashing in the Symposium and claiming that Socrates is his beloved likewise makes little sense without knowledge of the social context in which it takes place.

“For what is this love of friendship?  Why does no one love an ugly youth, or a handsome old man?”  Cicero

This ancient institution was also the backdrop for the accusation by Mark Antony -- reported by Suetonius -- that Julius Caesar’s adoption of Octavian, his heir, was based on such a follower/friend relation.

Hell Hath No Fury Like A Lover Scorned

According to Aristotle, the greatest source of instability in erotic friendship occurs when one of the parties misunderstands the nature of the relationship.

“The friendship that seems to arise most from contraries is friendship for utility, of poor to rich, for instance, or ignorant to knowledgeable; for we aim at whatever we find we lack, and give something else in return.  Here we might also include the erotic lover and his beloved, and the beautiful and the ugly.  That is why an erotic lover also sometimes appears ridiculous, when he expects to be loved in the same way as he loves; that would presumably be a proper expectation if he were lovable in the same way, but it is ridiculous when he is not.”

Navigating these relations and understanding how we stand to one another is one of the peculiar games people play on Twitter.  Each user profile provides two numbers that indicate how their role in the Twitter economy: “following” and “followers.”  Today Oprah Winfrey’s Twitter account says she has 1,125,560 followers, but only 14 friends.  She can be considered an extreme object of desire on Twitter – a megalos eromenos.  Other accounts will sometimes show a great disparity in the other direction, with many more friends than followers.  These people might be considered excessive lovers

A third group, exemplifying Aristotle’s notion of moderation, maintain balance between their “following” and “followers” numbers.  These might be thought of as the good citizens of the Twitter economy, since they seek neither to achieve status with the number of their followers, nor infamy through the number of people they are following.  Yet even this third group encounters its own problems.  When the good citizens of Twitter reach out to follow someone, they generally expect to have the favor returned.  If this does not occur, this can cause a certain amount of resentment against the beloved, in part because what was considered an overture of friendship has now been turned into an erotic and asymmetric relationship.

There is also some gaming involved in achieving high “followers” numbers – the number that is the de facto currency on Twitter.  One way to do it is to begin following everyone one can.  If they follow back, then this becomes a solid relationship of sorts.  If they do not, then the follower can later drop the offer of friendship, thus bringing his two numbers back into some sort of balance.

This in turn leads other Twitter account holders to be wary of new offers of friendship.  When it is from someone one does not know, the initial temptation is to simply say yes – and we all have early twitter relationships of this sort with people we do not particularly have any interest in.  Over time, however, we become wiser but less friendly which, in turn, leads to the problem of non-reciprocation resentment on Twitter.

Certain tools offer a way around this.  Rather than feel obliged to read the tweets of all 2000 or so “friends”, some account holders use software like TweetDeck to filter out their friends – in effect forming a circle of close acquaintances within their network of friends.  This isn’t foolproof, however, since if someone following you sends you a quick tweet, they generally expect a reply.  If you don’t reply, this may likewise eventually lead to non-reciprocation resentment – especially if the follower suspects you are filtering them.

The fault is in part due to the technology itself.  A technology that encourages asymmetric friendships will ultimately be based on relations of pleasure and utility rather than on Aristotle’s ideal of friendships based on the admiration of virtues.  This in itself is not a bad thing, but it lacks one of the central aspects of true friendship:

“In this noble relationship, services and benefits, on which other friendships feed, do not even deserve to be taken into account . . . For just as the friendship I feel for myself receives no increase from the help I give myself in time of need, whatever the Stoics say, and as I feel no gratitude to myself for the service I do myself; so the union of such friends, being truly perfect, makes them lose the sense of such duties, and hate and banish from between them these words of separation and distinction: benefit, obligation, gratitude, request, thanks, and the like.” Montaigne

At the same time, these Twitter relationships based on 140 characters at a time may form the basis for true friendships.  The people we follow and are followed by on Twitter may eventually be encountered in real life – at a conference; on vacation – and something more lasting may be formed, much as Montaigne and La Boétie’s friendship began as an acquaintance by reputation.  Even the relationship between the lover and the beloved in that peculiar institution of the ancient Greeks, according to Aristotle, has the potential to bloom into something closer to true friendship, after the initial courtship, if it is based on fondness rather than utility.

“Many, however, remain friends if they have similar characters and come to be fond of each other’s characters from being accustomed to them.  Those who exchange utility rather than pleasure in their erotic relations are friends to a lesser extent and less enduring friends.”  NE, tr. Terrence Irwin

Posted by James Ashley Friday, May 22, 2009 5:01:35 PM (Eastern Daylight Time, UTC-04:00) #    Comments [0]
 del.icio.us | DiggThis

 

All content © 2009, James Ashley
On This Page
Calendar
<July 2009>
SunMonTueWedThuFriSat
2829301234
567891011
12131415161718
19202122232425
2627282930311
2345678
Blogroll
Archives
Tag Cloud
Disclaimer

Powered by: newtelligence dasBlog 2.2.8279.16125

The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

Send mail to the author(s) E-mail

Theme based on design by Jelle Druyts