View Single Post
  #55   Spotlight this post!  
Unread 03-05-2011, 09:05
gblake's Avatar
gblake gblake is offline
6th Gear Developer; Mentor
AKA: Blake Ross
no team (6th Gear)
Team Role: Mentor
 
Join Date: May 2006
Rookie Year: 2006
Location: Virginia
Posts: 1,932
gblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond repute
Re: Losing on Purpose to Gain Advantage

Quote:
Originally Posted by Rick TYler View Post
We had this discussion with our teams and the conclusion was that if I ever had proof that one of our teams threw a qualifying match, either they could quit or I would.
By "threw a match" do you mean finding out after the match that they surreptitiously, and without the permission of their ally(s), used less than their full ability in order to purposefully lose a match? or do you mean announcing before the match that they and their ally(s) have agreed to not score because they all have determined that outscoring their opponents lowers the chances of at least one team winning the tournament (and the match outcome is irrelevant to any other allies)?

These are not the same situation. Everyone I know or have corresponded with agrees that the first is deceitful/bad/wrong/unethical and should not be entertained. I would call the it "throwing a match" and would tend to agree with your reaction.

The second is 100% out in the open, occurs by consensus, and might not be a bad thing to do in some very rare, but possible situations. I would not call it "throwing a match" any more than I would say that intentionally walking a batter is throwing a baseball game.

If you agree with the way I use the terms, then we might be on the same page. If you don't, reasonable people can disagree.

Under the heading of "Reasonable people may disagree", someone who considers using the latter option should perhaps either be dissuaded or told how to do it correctly; but they should not be scolded or threatened with figurative banishment, in the vehement manner most replies used.

Blake
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
Reply With Quote