Orcmid's Lair
Orcmid's Lair
status 
 
privacy 
 
contact 

Welcome to Orcmid's Lair, the playground for family connections, pastimes, and scholarly vocation -- the collected professional and recreational work of Dennis E. Hamilton

This page is powered by Blogger. Isn't yours?

Recent Items
 
Agreeing While Disagreeing
 
Addressing Customer Demands?
 
Crushing Supply-Push Under Demand-Pull
 
The fearful state of on-line students
 
The Final Page
 
Oh, the tragedy, the humanity: Donate Now (amazon link)
 
The Asia Disaster: Aiding the International Relief Effort
 
Tsunami - Earthquake - Supporting International Relief
 
The Heart of Trust
 
Accountability: Lessons from Engineering and Medicine

2005-03-12

Agreeing While Disagreeing

ACM News Service: New Software Takes Guesswork Out of Tough Decisions.  In discussing processes for arriving at group solutions, it is usually considered esssential to find areas of agreement and alignment on a view of the world before proceeding.  It may be that differences in ideology don't matter.  This blurb reports on work by Steven Popper on modeling systems that determine outcomes that work under a variety of initial assumptions, thereby allowing people to align on a model that accomodates their separate views.  I take this to mean that agreement can be found among parties with different agendas simply because the likely outcome is agreeable anyhow.  Thus emerges an occasion for violent agreement, perhaps.

My understanding of the import of this approach (without assuming that it really removes guesswork and especially taking courage to risk a choice) is illustrated by the current dispute over the 2004 Washington State gubernatorial election.  I can support the remarkable work of Stefen Sharkansky in identifying irregularities in the election without supporting Stefen's expressed agenda and definitely without ideological alignment with those who provide either supportive or detracting comments on his blog.  I am not aligned with either declaring a different winner or with there being a special run-off not provided for in current law nor the state constitution.  I am satisfied with the judge voiding the election because the process is so flawed that the outcome is not determined (the race being so close and the noise in the process being greater than any assumed margin of victory for any candidate).  I am also satisfied with anything else the court is likely to determine.  And I am wholeheartedly in support of the work that a few diligent citizens have invested in exposing just how careless we have become in the handling of elections here.  It is not hardly a space-shuttle disaster, but the parternalism and carelessness with the franchise is startling.  I trust the judge more than the officials of King County, where the outcomes of these close statewide elections are essentially determined and where the absence of diligence is a lesson in sloppiness.  I use this as an example of agreeing on a course of action without attaching the same significance to the prospective outcomes.

I don't think the Popper CARs program will help us in my example, since the time of voting or election is too late.  I would expect Popper's approach to be helpful in the formulation of proposed legislature as well as in non-elective bargaining and problem solving.

The 2005-03-02 Kimberly Palmer GovExec.com article provides the original account.  I did some searching and found more useful materials than I can digest here, here, here, and here.  And then here.

 
Comments: Post a Comment

2005-03-11

Addressing Customer Demands?

ACM News Service: Companies Seek to Hold Software Makers Liable for Flaws.  This blurb summarizes the tension around product liability for software, especially for security vulnerabilities.  The creation of liability principles might be the death-knell for smaller software firms and yet it seems that something must happen.  The Oracle chief security officer warns that government regulation may be the only possibility unless "software makers demonstrate that they are responsibly addressing customer demands for improved security."

The Wall Street Journal's David Bank article is available after registration at ContraCostaTimes.com.  My favorite additional quotation on the lack of accountability of software makers is this:

"We ought to have some way of holding them accountable," says Daniel Wolf, director of information assurance for the National Security Agency, who oversees a system for certifying the security of software for government use. He says Congress would be quick to intervene "if something bad happens and it's because of bad software."
It also seems that there is a great rush to close the kimono to avoid liability, in that full disclosure may invite action.  It would be interesting to know whether that feared-risk is anywhere as dangerous as the liability that occurs when information is willfully withheld.

And mostly I wonder, "why not transparency for its own sake and out of willful determination to serve our customers, the industry, and society?"

 
Comments: Post a Comment

Crushing Supply-Push Under Demand-Pull

ACM News Service: The "Pull" of Niche Communities.  The collision of demand-pull blogging with supply-push media-monopoly approaches is used by John Seely Brown to illustrate how the knowledge economy transition to niche communities, open source, and open content is disrupting the system.  JSB also fingers institutions of higher-learning among the change-resistant.

The full interview is found in Mary Grush's Campus Technology magazine article.

 
Comments: Post a Comment
 
Construction Zone (Hard Hat Area) You are navigating Orcmid's Lair.

template created 2002-10-28-07:25 -0800 (pst) by orcmid
$$Author: Orcmid $
$$Date: 05-04-17 22:31 $
$$Revision: 1 $

Home