[sdiy] ot: is it true that Waldorf crashed?

[Paul Maddox]

Grant,

> Again, sorry, but that would cover just about any project involving
software
> development that I have been on. I have never yet seen an implementation
> that achieved 100% of the software goals.

thats NOT what I said..
the bug list for Q is about a mile long, no exaggeration..
Waldorf have been promising for well over a year to release a new OS which
fixes a large portion of these..

> This is in spite of super-human efforts on the part of the engineers,
> software and hardware. The debugging can drag on for years.

I agree, but you should do one of two things
1) Tell the customers there's an OS update comming, SHORTLY before
releaseing it
or
2) Don't tell them until its ready.

You can't keep saying, "its nearly there" for a year!
As anyone about Waldorf and "S.O.O.N.".

> I place the blame on management, who only think software engineers are
> working if they are typing. They best software engineer I worked with
would
> spend 8 weeks defining a program and two days typing it.

I also put the blame on management for failing to see that you need to keep
customers happy in order to keep them.

> But he was always under tremendous pressure from the engineering manager
"to
> be doing something". (i.e. why aren't you typing every day)

Thats because managers don't understand, good managers come from people
who've been there and done it.
But that seldom happens as most programmers enjoy the work..

Paul