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

Paul Maddox P.Maddox at signal.qinetiq.com
Mon Feb 23 10:01:09 CET 2004


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.

Im not saying 100%, Im saying fundementals, like staying up without
crashing.
Take the waldorf wave, great synth, poor OS, crashes very very often..

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

agreed, but before releasing a product, it should at least be able to stay
up and be used for > 1 hour!

> 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.

Partly, but also market preassures, everyone wants everything NOW..

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

yep, agreed.

Paul



More information about the Synth-diy mailing list