Always wonder why your project doen't work ? Check out the flowchart ;-))
5 Comments
a) wrong symbols
b) no exit condition for the "you poor bastard" loop.
a can be overlooked....
but "b" is a fatal design flaw!!!
needs a block between "can you blame someone else?" and "You poor bastard" perhaps a procedure "Locate alternate scape-goat" that then connects to "No Problem"
review this mod ....
LOL!... I think you can get into an infinite loop if can't blame someone else, so hire more consultants... ;-)
I think Denny is incorrect, the infinite loop is valid until the "can you blame someone else" condition becomes true. Thus his "find alternate scapegoat" procedure is already implicit in the diagram.
It would be contradictory to go directly from "can you blame someone else - NO - find alternate scapegoat [ie., blame someone else]."
Well if "a" were fixed..... :-)
"IF" should be a diamond not a box.
:-p
However it might be a good idea to put a "sleep" before the test...that way you're periodically polling for a new scapegoat, instead of consuming all processor with that loop...the length of the delay could depend on severity, going to zero if the lack of a scapegoat will cost you your job :)
