Re: PB10: Packets in the chat room

You know, Patrick, I truly appreciate having you
around. If you continue with this line of commentary,
people will forget most of the gems I have stated over
the years.

Penn Bowl made only one mistake of
a major note. It featured a mislabelling of
packets. That's IT. Compared to the downfalls of other
tournaments involving packet submission, that seems trivial
by comparison. And believe me, if the worst thing
people say about my tournament next week is there was a
mixup near the end with some packets, I'LL be happy,
because that means the rest was fine.

Furthermore,
the packets themselves were very well-edited, as
complaints within the team were reduced to individual
questions ("cricket"?), which when placed among the sea of
other absolute gems. The great thing about Penn Bowl is
the variety that populates the packets -- one round,
you'll get a high scoring slugfest; the next round, you
may find yourself in a war of attrition; then again,
it may be right up your alley; or perhaps, you'll
find yourself making mistakes. Since you're almost
never able to sustain "hot" or "cold", each round is a
mini-tournament in itself -- fortunes can change in an instant.


Example: We were 4-2 after the evening, with losses to two
teams we felt we could have beaten. I was upset at the
sloppy play and figuring our chances of making the
playoffs were over. Not only did we make the playoffs, we
came within 50 points of running the table Saturday
and earning a top seed! Simply put, every game is
winnable, and that's fun for all 64
teams.

Obviously, Patrick, you were at Penn Bowl or heard about it
from someone. If this is your first contact with the
event, then your commentary is unnecessarily harsh.
These are mistakes I have made -- judging with too
little information -- and they can give yourself and, if
people know it, your organization a black eye. Next
time, consider the positives before railing on the
negatives. Not every tournament is to be judged on a slate.
Sometimes, it's best to let it be.

Andy Goss
Duke
University Academic Team

This archive was generated by hypermail 2.4.0: Sat 12 Feb 2022 12:30:43 AM EST EST