email chain/email for comments: drewgartner1@gmail.com

Debate background:

Iowa City High: '11-'15
University of Iowa: '15

Coaching: Iowa City High '15-'18. '21- present

Important disclaimer: I have done nearly 0 research on this topic, and will likely not understand your acronyms without explanation. Please do not assume that I have a shared knowledge of the topic, and take time to explain things.

Important Disclaimer Addendum: My comfortability with full mega-speed has lowered, especially in the realm of analytics. I would like your analytics to be slower, so I can really get it all down. Taking a few year break from debate really impacted my full spread comprehension.

I debated Policy all through high school and did some college policy as well. I mainly work with novices, now. Topic specific acronyms, let me know what they mean I won't know. Don't start your speeches full speed, start at 80% and work up to full speed.

I think most debates can/should be decided without reading evidence. This means it is the debaters' burden to tell me what the evidence says, and the implication of the evidence. This also means that I reward story telling/writing my ballot. I have no sympathy for debaters who ask about "well, what about this evidence that says x" after I give a decision. I will not be embarrassed to vote against an argument that I feel i do not understand. It is your job to tell me about that evidence and why it matters, not my job to read it and implicate it on the debate.

General Philosophy: I come from a team where our primary focus was "traditional policy debate" meaning we liked to read heg, environment affs, et.c. Our main neg strat was the DA and a CP, and that is the type of debate I prefer. I did do a lot of cap debating, and a fair amount of security debating, too. My knowledge of critical theory is very limited and I probably require a huge amount of work on the more "out there" ks to vote for you. That being said, I do believe a dropped argument is a true argument. I will vote on dropped arguments if they are dropped and explained. As a caveat, debaters tend to have bad flows and claim everything was dropped, when the reality is that they probably did not. Please do not use the term "functionally conceded" in front of me, that term makes no sense. Either they have dropped something or they have not.

Specifics:

Disadvantages- Probably my favorite part of debate is the top level interactions with case and good DA O/Ws and Case O/Ws and turns debates. These are probably where the majority of my decision calculus comes from. Obviously, you need to win risk/chance of your disadvantage being true, but good impact calc and turns debates are very convincing.

Counter Plans- there tend to be a lot of cheating counter plans, and as a 2a I am probably sympathetic to reasonable theory arguments and perm do the counterplan. That being said, most counter plan theory should be a reason to reject the argument, it will be extremely difficult to win that it should be a reason to reject the team

Ks- like I said above, i am mostly versed in cap and security. If you want to read too much beyond basic Ks, I am most likely not your type of judge. Floating PIKs are probably bad, don't let the negative get away with them.

"non traditional debate/ performance"- also not very versed in it. I am more than likely not the type of judge for this, but i will not reject any arguments out right. I am pretty sympathetic to FW arguments. However, if you are a "non traditional team" and you get stuck with me as a judge, don't lose faith, I can be persuaded. I enjoy critical affirmatives that actually engage the topic, not just reject debate outright, and plan texts are preferable.

T- I don't know much about this topic, so all the topic specifics should be slower and well explained. I think that most debaters try to go too fast in their final rebuttals on T, which leads to a lot of judgement calls. To remedy this, go slower in your final rebuttal, and you will be rewarded.

Theory- Most things are reasons to reject the argument not the team. I will probably not vote on dropped perm theory, even if you claimed it was a reason to reject the team.

Speech Docs/ Email chains

I would prefer if all debates were done with email chain. Please add me to the email chain at drewgartner1@gmail.com
I can tell when you are wasting time and/or stealing prep. DON'T. it's annoying, wastes everybody's time, and will undoubtedly lose you speaker points. technical issues do happen, yes, but they should be resolved quickly and efficiently. I would prefer every speech to start as nearly as immediately after prep or CX as possible. We don't want to be the last round done.

Speaker Points

It's very easy to impress me, using technical skill and clarity.
I am okay with speed, but will yell clear once or twice before the speaks begin to get docked. Nobody likes kids who are fast but incoherent, going slower is in your best interest.
Being nice/reducing all hostility is very preferable. If you have made it this far and are still reading, I will likely increase speaker points if you work "jambalaya of awesomeness" into one of your speeches, especially if you are original and make me laugh rather than just saying it to say it. I have a relatively low threshold for docking speaks due to hostility. Being assertive and being aggressive are much different, know the difference. I probably will not say anything if you are being overly rude/rude at all, but it will significantly hurt your speaker points, but will not affect the decision calculus.