[Sigia-l] Pillars of Ergonomics

[Livia Labate]

: An unimplemented idea is...nothing.

In my experience badly implemented ideas are the cause of much rework and
headaches. I am obviously not saying not to implement ideas, of course, but
to figure out 'why' they are being implemented, not just how they can be
implemented.

: While they may appear to be distinct they are not unrelated.

I entirelly agree.

: The implementation language/technology tells you not only how to do things
but
: also, and this is important, how you cannot do certain things.

That would make us very mediocre people (to let a language or technology
limit our ability to do certain things). New languages and technologies come
to be preciselly because we convey new structures we can't implement with
what we have.

: It's a matter of efficiency: why waste time with stuff (why)
: that you cannot implement (how).

You talk about the importance of implementing things regardless of the why
("An unimplemented idea is...nothing") and say this is a matter of
efficiency? What's the use of efficiency without efficacy?

[efficiency as in 'doing things with the least amount of resources' (fast &
cheap) and efficacy as in 'doing something that attains real preconceived
goals (adds value)']

I'm surprised that you of all people would say that. What's the point of
having information architects, business analysts, designers, etc, then, if
we can totally rely on programmers to deliver great efficient solutions?

They're only delivered efficiently, they aren't even necessarily used
efficiently.

: Yes, knowing the how of
: implementation won't miraculously render you
: a good designer, but it can make you a better, more efficient
: designer/communicator.

We are still agreeing. I'm just perplexed by your sudden enthusiasm with
technology despite of results.

-LL