| > Getting to work effectively with Digital products is a lot like dating
> a very shy person. It takes a very long time to get to know them. And
> eventually you get frustrated how long it took to get to know the
> person, in spite of the benefits, and have the feeling of "why didn't
> you tell me this earlier..." about very simple things about them. It
> can be a thoroughly frustrating experience...not at all rewarding.
Just curious...have you been talking with my wife?
|
|
I think part of the problem is that engineers are typically left to
figure out the product requirements for themselves. Left to their
own devices, engineers will naturally do the best they can at building
at building the best solution to a stated problem. When Digital has
an engineering process in which requirements are defined formally,
signed-off by sales and marketting, and when adherence to requirements
shows up in the reviews of engineers and their managers, then sales
and marketting will get what they ask for. Digital has the same kinds
of engineers that other companies have, by and large. What we need is
the same or better process.
BL (engineer, ex-Pittsburgher)
|
|
you must be talking about OSI (or MSU or MCC ......)
takes a long time to know em and once you do, you realize that you hate
em and wished you'd never taken the time...then you find out that no
one else can stand em either but have been forced into their
association....then..just when you think you are getting to know them
enough to tolerate their presence, they die. (and you start to wonder
about the power of wishful thinking...)
|