Site FeedPalimpsest has moved. Please visit our blog in its new location for the most recent posts from Scriptorium.
Palimpsest
DocTrain: Keynote from Kelly Stirman
Thursday, October 18, 2007 — posted by Sarah
Kelly Stirman of Mark LogicMost important trend: task and role aware publishing
What if a phone were aware of meeting times and automatically went into vibrate mode?
Documentation: When editing CSS in Dreamweaver, O'Reilly book on HTML should display the relevant CSS information.
Lexus: A customized car manual with relevant color, my name, my options.
Electronic flight bag: Provides supporting information that is relevant to current status. (No takeoff information when cruising at 30,000 feet.)
A highly visual presentation, which loses a lot in a blog. A discussion of different types of hammers, ranging from a rock to the innards of a Steinway -- we want to create the right tool for the right job.
How to get to task and role aware:
- XML
- granular access
- content logic
Language and meaning are two very different things.
XML is also the Socratic method. Communication using a predefined set of rules.
Schema or DTD is a contract.
Oops. Now we're doing an XML overview. Nice overview, but appropriate for this audience?
Why XML?
- Distinguish between meaning and rendering (i.e. separate content and presentation; we've heard that before)
- Relationship between meaning and rendering can be many-to-many. One piece of content, many types of output. Also, one type of output, many pieces of content as input.
- Library: basically a "self-service" model. You go to the library to find your books.
- Books are atomic -- you can't break a printed book into smaller parts -- you can't check out a chapter from a library.
- Need a query language for a tool (this is where we veer into the business case for Mark Logic products)
- Example: SafariU. Custom course readers for university professors.
....and he's running over his time, so I must go.
Mr. Stirman is trained in philosophy and it shows. Very interesting presentation, and a different perspective from what we're used to.
Labels: conferences, doctraineast07
9:08 AM Permalink | |
DocTrain: Keynote from David Platt
— posted by Sarah
I'm at DocTrain East in Boston this week.We're starting out with a keynote from David Platt, author of Why Software Sucks...and what you can do about it.
Internet users in 1994 were almost exclusively academics/researchers; about 2 million total. Lots of technical support; no deadlines.
In 2006, we have 1 billion WWW users and almost all of them are using personal computers. New computer users and no support.
Platt's First, Last, and Only Law of User Experience Design:
Know Thy User for He is Not Thee72% of adult population doesn't have a college degree, but of course software is developed almost exclusively by people with college degrees.
"Normal people don't drive stick shifts". But a lot of programmers prefer them -- inconvenient but more control. Software developers like the process of driving the car; normal people prefer to just get there.
Software applications tend to sacrifice ease of use (which developers don't care about) for fine-grained control (which developers do care about but users don't).
Users just want the software to work.
Interfaces matter -- the example is ups.com, which is pain to navigate. However, you can drop a UPS tracking number into a Google toolbar and get the tracking information in one click. Thus, Google is a better UPS tracker than ups.com.
Constant friction -- extra clicks cost money because they take time.
Catastrophic error -- Mars Orbiter, medical errors...
Personal public ridicule -- People publish lists like "web pages that suck"
Five ways to make a project suck less:
1. Add [a person who does not know the internal workings of the software] to the design team. I think he might have lost some of the audience when he said that tech writers would be ideal for this.
2. Break convention when needed (Quicken/MS Money never offer to save your content; they just do it.)
3. Don't let edge cases complicate the mainstream
4. Instrument -- carefully. Use feedback agents to get information about how software is being used.
5. Always ask: is this design decision taking us closer to "just working" or farther away?
Entertaining, but he's used to presenting to nearly all-male, all-programmer audiences, and much of what he's doing here was preaching to the choir.
Labels: conferences, doctraineast07, humor
7:56 AM Permalink | |