Re: Six Sigma (was: something else)
spinoza1111_at_yahoo.com
Date: 01/25/05
- Next message: gooch: "Re: What is UML?"
- Previous message: Jim Rogers: "Re: best approach to develop running software"
- In reply to: Programmer Dude: "Six Sigma (was: something else)"
- Next in thread: Randy Howard: "Re: Six Sigma (was: something else)"
- Reply: Randy Howard: "Re: Six Sigma (was: something else)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 24 Jan 2005 19:49:21 -0800
Programmer Dude, it appears that Howard had a failure in the book code
despite its use of error handling. The error handling includes
try..catch blocks for any situation that it "open ended ": these are
situations where the amount of resources may not be available, etc. For
example, all reference objects are created not when declared but in
try..catch. Also, a new inspect() method and methodology, described in
the book, are used to check object status.
My problem here is that a thief (Randy Howard) has downloaded the code
without buying the book and found a bug despite my good praxis.
If you've used best practice and a bug occurs, I am hopeful that you
know what the next step is. It is called follow up, in which I check
the code on a high-end machine, using Randy Howard's limited
information. I am reluctant to contact him by email because of his
issues therefore will have to do the best I can with the information
available.
There is as you know an entire courtesy of bugs. The reporter doesn't
crow lest he eat crow, and the bug author gets off his f*g ass, and, if
the bug exists, fixes it. Nobody tells the manager unless they have to
lest the manager have a heart attack: instead they fix the bug.
[Sundar and I found, at the last minute, 256 stored procedures which
need to be converted. I gave Sundar a parser and he fixed the problem
overnight. Had we told the manager, he would have had a fit, and had us
spend two weeks working by hand to repair the bug.]
However, I am familiar with what happened to "structured programming":
it was all too often in my experience trumped by "office politics".
Here, the politics is national.
Randy Howard is clearly a Red State head case, and the Bush programme
is to gradually exclude all nonconformists not only from governance but
from civic society. The programme in fact resembles that of Germany
between 1933 and 1938, during which Jews were eradicated, gradually,
from the professions...in such an incremental way that there was a net
in-migration of Jews into Germany in 1935.
I am uniquely fortunate in finding a job in the People's Republic of
China in this context while being fully aware that in the words of my
Lonely Planet guide to China, it is a "police state".
Years ago, Mr. Dude, the right-wing, short-hair, Nixon-voting data
center manager, who was engaged in a campaign to boot me out of the
center although I worked for a user, found my assembly code on a desk.
He immediately gave up his campaign and had for me some kind words,
which I appreciated. This great man, whose greatness was of the sort
that cries out in the streets, and is not heard, practically discovered
the Y2K problem and published a book about it in 1985. He remains a
right wing head case and a great man, and his name is Jerome Murray.
Today, the stakes are higher and no sense of community exists, this I
well understand. Nonetheless, I shall follow up as best I can on what
dual processor SMP boxes DO when they run "my" code.
- Next message: gooch: "Re: What is UML?"
- Previous message: Jim Rogers: "Re: best approach to develop running software"
- In reply to: Programmer Dude: "Six Sigma (was: something else)"
- Next in thread: Randy Howard: "Re: Six Sigma (was: something else)"
- Reply: Randy Howard: "Re: Six Sigma (was: something else)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
