Irony (ADMIN: HTML (Web Site) Training Workshop....)

[Arlen -dot- P -dot- Walker -at- jci -dot- com]

It strikes me that:

1) We're very quick to complain that users don't read what we write before
calling tech support, complaining about the product, etc.

2) We also, (as evidenced by the numerous times things similar to the
original subject here have come up) apparently do not read instructions
placed before us.

<Pause for irony appreciation>

OK, now that's over with, let's toss out some questions:

1) Why don't they/we read?

2) Is it the writer's fault or the reader's fault?

3) What can the writer do to a) remedy the fault, if it is the writer's b)
encourage the readers to overcome it, if it is their fault?

Especially interesting will be factual answers to questions 1 & 3,
including supporting data. Q2 is, of course, subjective.

Have fun,
Arlen
Chief Managing Director In Charge, Department of Redundancy Department
DNRC 224

Arlen -dot- P -dot- Walker -at- JCI -dot- Com
----------------------------------------------
In God we trust; all others must provide data.
----------------------------------------------
Opinions expressed are mine and mine alone.
If JCI had an opinion on this, they'd hire someone else to deliver it.