BV> All they had to do was buy a bunch of Nerf bats, charge $5 per
 BV> person, and change the name to  "Whack the
Developer."
 BV>  What windows developer would not pay $5 to whack the
 BV> designer of GDI, or the author of DDEML ? Most programmers I
 BV> talked to agreed that Microsoft could make a(nother) fortune
 BV> this way, but C/C++UJ Managing Editor Marc Briand cautioned, "I
 BV> think that could get out of hand pretty quick."

  ROFL!!! Everyone would rush in and kick the bastards to death!

  I wonder how they actually develop this stuff? I was comparing the
design of a TV set to a large program with keith, and I realised that
it's a valid comparison. The T-29 was 20,000 man-hours, and that's a
pretty big program if you put the same effort into writing code. It 
has to be split up, and there has to be an overview with one person 
in charge or it doesn't work.

  keith was talking about his own experience, with standard interfaces
between various parts of the program; the same way that ant's dickhead
with the video machine was talking, and that just doesn't work! The
interfaces end up the main part of the project! The tail wags the dog.

  It dawned on me that as soon as a program gets larger than one
person can assimilate, and "know" properly, then the wheels have to
fall off. This must have happened at Microsoft and IBM already. They
create monsters that no one really understands, all patched together
with sticky tape showing the joins.

Regards,
Bob
 
___ Blue Wave/QWK v2.12
@EOT:

---