When I posted this joke about a nice f... Flowchart, I didn't expect to have you guys discussing about 'intersections being wrong..' or 'If condition between X and Y'.
Serious guys you're crazy and I love that...continue ;-))
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"
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]."
Feedback
denny
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 ....
SBC
LOL!... I think you can get into an infinite loop if can't blame someone else, so hire more consultants... ;-)
Dennis
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]."
denny
Well if "a" were fixed..... :-)
"IF" should be a diamond not a box.
:-p