Originally posted by PinTBC Originally posted by Forbin
Good idea. Make sure you get those 6 WR sets taken care of in case Bort adds it...
Direct snaps rule.
All, you are doing is proving that you are not a person who understands design in the slightest. If you did, you might recognize an if..then..else structure.
But don't let your ignorance get in the way of your witty posts, and stupid remarks.
PinTBC
if ($poster == "PinTBC") {$fail = true}
Go ahead and come up with a reason that Bort added 6 WR to the options. I'll be waiting while you explain his obvious coding mistake to an experienced coder.
Go ahead and come up with a reason that Bort added 6 WR to the options. I'll be waiting while you explain his obvious coding mistake to an experienced coder.
OK, design 101
Don't need a reason, when you design something (in this case a defensive set of plays), you should always have an else condition.
So in our case, I have a 0-2 WR set, a 3 WR set, and an 'else' condition.
Anytime you design a state machine, case statement structure, or if.. then.. structure, you must make sure that all undefined cases are caught in the 'else' condition or you risk your design being unstable. It is one of the very first 'rules' you should ever learn when designing digital or software structures. Granted software has moved quite a ways now a days, and some of the autogenerating code automatically traps out the unknown states and flags them as errors, but it is the same rule.
I make that statement as a design engineer for the last 24 years. Over the last 15 or so years, I've had the pleasure of actually forming teams and designing some very cool shit.
Originally posted by PinTBC Originally posted by Forbin
Go ahead and come up with a reason that Bort added 6 WR to the options. I'll be waiting while you explain his obvious coding mistake to an experienced coder.
OK, design 101
Don't need a reason, when you design something (in this case a defensive set of plays), you should always have an else condition.
So in our case, I have a 0-2 WR set, a 3 WR set, and an 'else' condition.
Anytime you design a state machine, case statement structure, or if.. then.. structure, you must make sure that all undefined cases are caught in the 'else' condition or you risk your design being unstable. It is one of the very first 'rules' you should ever learn when designing digital or software structures. Granted software has moved quite a ways now a days, and some of the autogenerating code automatically traps out the unknown states and flags them as errors, but it is the same rule.
I make that statement as a design engineer for the last 24 years. Over the last 15 or so years, I've had the pleasure of actually forming teams and designing some very cool shit.
But you have a lovely day.
PinTBC
You can't be that fucking stupid. Seriously. 6 WR?
You can't be that fucking stupid. Seriously. 6 WR?
yawn,
I knew I should have just gone to bed.
You need to learn to read. I have a setting which is 4+, and includes any set of receivers greater than 4. It really isn't a tough concept.
There isn't a 4 WR set, but since I'd use the same defense as the 5 set if Bort ever put it in, why fuck around. I'd have to create a set for the 5 WR, and the 6 on that is just because it is the outside limit of the slider.
Yes, I know that there is no 6 WR set, but why would I limit it to less than the slider allows? It's not like I made up a specific defense trying to stop someone running 6 WRs, I simply extended my 5 WR set to cover anything greater than 3 WRs. It really isn't that tough a concept.