Re: What ONE thing should the CIO understand about managing/motivating developers?

Malcolm McLean said:

<snip>

Projects tend to fail when
someone in authority, who is not directly involved in code, has the power
to insist on late changes to the specification. The problem is that the
change can usually be accommodated, but at cost of degrading the
structure of the rest of the code. So bugs appear elsewhere, and
eventually the project fails. I've seen this countless times with games -
the companies I worked for are now bankrupt.

These are the same companies that showed contempt for their customers by
passing off any and all bugs as "dirty disc"? If so, I won't be shedding
any tears for them. A company that lies to its customers deserves to fail.

--
Richard Heathfield <http://www.cpax.org.uk>
Email: -http://www. +rjh@
Google users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999
.