Blunder Dome Sighting  
privacy 
 
 
 

Hangout for experimental confirmation and demonstration of software, computing, and networking. The exercises don't always work out. The professor is a bumbler and the laboratory assistant is a skanky dufus.



Click for Blog Feed
Blog Feed

Recent Items
 
Pimping up Scampo: From Media Center to Media Prod...
 
Identity - Not Just the Law Any More
 
Mark Guzdial and the Computer Science Education Tr...
 
Does Visual Studio Rot the Mind?
 
Grady Booch on the Limits of Software
 
Modeling the Office Open XML Packaging Conventions...
 
Appreciating ALGOL 60: Launching Computer Science
 
Orcmid's Lair: Global Social Identity
 
What We See Is Not What We Get: Character Codes an...
 
Blinking at Quarks: Is It an Object that I See Bef...

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

Locations of visitors to this site
visits to Orcmid's Lair pages

The nfoCentrale Blog Conclave
 
Millennia Antica: The Kiln Sitter's Diary
 
nfoWorks: Pursuing Harmony
 
Numbering Peano
 
Orcmid's Lair
 
Orcmid's Live Hideout
 
Prof. von Clueless in the Blunder Dome
 
Spanner Wingnut's Muddleware Lab (experimental)

nfoCentrale Associated Sites
 
DMA: The Document Management Alliance
 
DMware: Document Management Interoperability Exchange
 
Millennia Antica Pottery
 
The Miser Project
 
nfoCentrale: the Anchor Site
 
nfoWare: Information Processing Technology
 
nfoWorks: Tools for Document Interoperability
 
NuovoDoc: Design for Document System Interoperability
 
ODMA Interoperability Exchange
 
Orcmid's Lair
 
TROST: Open-System Trustworthiness

2006-08-03

 

Design as Choice: Eugene Wallingford

Knowing and Doing: Design as Choice.  Eugene Wallingford has an interesting riff on what design is and the ways that design emerge and the tension between design as specified and design as discovered.  It reminds me that at one point I responded to an interview “why do I need an architect?” question with “to keep your options open.”

{tags: }

I am engaging in a toy illustrative design/programming exercise that demonstrates how we can establish portable arrangements for what must have platform-specific implementation: isolating platform dependencies in a way which minimizes the dependency surface and has the dependency be maintainable in the face of multi-platform migration.  What's particularly revealing to me is how this tiny worked case is revealing to me how much my design sensibilities have matured certain respects without having paid direct attention to it.  I am also learning about the difficulty of edge cases and proper testing for the case that I chose to illustrate.

I think the tension between specification, exploration, and discovery/refinement has to do with designing on purpose.  That is, having it be “by design.”   It is the case that all artifacts, especially software ones, exhibit architectures.  The goal is to accomplish an architecture or design on purpose rather than by accident.  There is something to be gained by having enough (but no more) up front, especially with regard to the embodiment of essential requirements and to the identification of the invariant parts that one is committed to preserving in the face of and in spite of whatever else happens.  One might learn that original design points cannot be satisfied or preserved, and that is also something to address explicitly when it occurs.

Although, even in my simple example, I am discovering a great many aspects of the problem that I did not appreciate when starting out, despite the fact that I did specify my approach in advance and I have not provided much confirmative program code so far, I don’t think I would have noticed so much in my explorations if I had not started with a trial specification which is still being refined as I work out the demonstration.

 
Construction Structure (Hard Hat Area) You are navigating Orcmid's Lair.

template created 2004-06-17-20:01 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 10-04-30 22:33 $
$$Revision: 21 $