Cory Freivogel
07-27-10, 07:28 PM
CORY FREIVOGEL JUDGE PHILOSOPHY
Hi! My name is Cory Freivogel. I did four years of policy debate in high school in the Chicago area. After that, I spent four years doing Lincoln Douglas and Parliamentary debate at McKendree University. I’m currently the assistant coach there.
I will preface this philosophy in the way that most people do - I think you should debate however you debate best in front of me. That being said, I obviously have certain biases and I think you should be familiar with them.
Some general notes….
1. I think debate is first and foremost a game. I think you should do whatever it takes to win that game, and I respect people who play the game with a lot of heart and lot of intensity.
2. I like people who do work. This doesn‘t mean that I won‘t vote for lazy, trite strategies - I have no problem doing that. It just means I respect people who put in extra effort to develop or update sweet arguments.
3. I like people that talk pretty. I certainly don’t think you should ever sacrifice strategy and execution for eloquence, but if you can give a smart speech that’s funny and engaging it will bode well for you. Also, don’t try to be funny if you’re not.
4. Don’t dismiss defensive arguments. Of course I think you should be making a wide variety of offensive arguments, but do not assume you’ll be fine by saying that 9 smart, defensive answers to your affirmative are just defense.
DISADVANTAGES
I like these arguments a lot. Running well-researched disadvantages with a diverse set of link arguments and huge probable impacts is the easiest way into my heart. Generic disadvantages like politics, business confidence, etc. are fine as well so long as they’re specifically tailored to the affirmative and properly executed.
Similarly, I think smart negatives (and affirmatives as well) will do a great deal of work comparing impacts. If you do not do this I will make my own determination about the probability and magnitude of a disadvantage’s impact. I am also probably more concerned about probability than some other judges may be. I am not often impressed by massive impacts that are highly improbable and under-explained. Phrases like “even a 1% risk of our impact outweighs the entire risk of the aff” are typically code for “our impact is absurd and our disadvantage barely links.”
COUNTER PLANS
These arguments are sweet as well. I typically err negative on arguments like PIC’s bad, conditionality bad, etc. I will vote on these arguments, but it will be an uphill battle. The argument that I should reject the argument rather than the team is usually a winner. I think condition, consultation and other silly process counter plans are of questionable legitimacy and I can definitely be more persuaded to drop teams on theory if they’re extending these arguments. That being said I like counter plans of all shapes and sizes and think that if you aren’t reading one or straight turning the affirmative, then you’re probably in trouble.
KRITIKS
I am not as hostile to these arguments as most people probably think I am. I am, however, probably as unlikely to understand these arguments as most people think I am. I have not and probably will not ever read any traditional or post-modern philosophy unless someone requires me to do so. I’m not trying to dog on anyone that does, but it’s just not my thang. This is mainly meant as a word of caution. If you run the kritik I will listen, flow and do my best to make a fair decision. But, I am not the best critic for you. If you somehow find me in the back of the room and you have nothing but your criticism, it will serve you well to slow down and eliminate all the jargon you imagine I may be familiar with.
That being said, if you’re an affirmative answering these arguments do not assume I will let you get away with answering kritiks poorly. If you mischaracterize the criticism, concede framework arguments, or rely on defense then I’ll probably notice and you’ll lose.
TOPICALITY
I like good topicality debates a lot. If you are affirmative, then you need to meet the interpretation or you need a counter interpretation. Absent one of those things, you will probably lose. If you are going for or answering topicality you should be comparing standards and voting issues in the same way that you compare impacts. If you do not compare standards, it will make it very difficult for me to make a good decision and it will be bad for everyone. I am also more persuaded by arguments about ground than limits. I could care less if your interpretation “explodes the topic” given that the topic will only exist once and you don’t have to do any research in the future.
ASPEC / OSPEC / FSPEC / BILL NUMBER SPEC / COMMITTEE ORIGINATION SPEC / BLAH BLAH SPEC….
These arguments are really not my cup of tea. This is mostly because I don’t like giant pieces of shit in my tea. I understand the strategic utility of introducing these arguments in the LOC, but I cannot understand why one would choose to extend them in the MO unless there was some incredible example of abuse. It is difficult for me to imagine giving any higher than a 27 to even the most persuasive extension of a generic specification argument.
THE CASE
People forget about the case all the time. That makes me sad because I love a good case debate. If you’re the LOC and you don’t have an incredible counter plan, then you should be putting a lot of offense on the case. Similarly, the MG should be extending and utilizing the case throughout his or her speech. It frustrates me to no end when affirmative teams assume they can entirely ignore the case until the PMR when it suddenly becomes the focus of the debate. Personally, I think you should have to extend the affirmative throughout the debate.
POINTS OF ORDER
I keep a pretty decent flow and think I can detect new arguments on my own. That being said, they are allowed by the rules and if you think there is a particularly egregious example of an abusive new argument feel free to call it. However, if I know an argument is new I will protect the opposite team regardless of whether or not you say it's new. If you call a bunch of unnecessary points of order on teams just to disrupt their speech or be funny or whatever I will be very unhappy. I hated when teams did that when I debated and I imagine I will hate it even more as a judge. Don't do it.
POINTS OF INFORMATION
I think as a general rule you should probably accept two of these per speech. I could pretty easily be persuaded to pull the trigger on a "they didn't take any questions" type of procedural. Also, no means no. If someone won't take your question don't yell that question or jump around waving your hands like an idiot or yelling "Please!! Just one!!" The only exceptions to this are in instances when you need to know the status of a counterplan or to have a text repeated / handed to you. I don't think you should have to raise your hand to ask for those things. Maybe there is no legitimate justification for that, but that just happens to be what I think.
OTHER THINGS…
You can go as fast you like so long as you’re clear. I went pretty quick when I debated and its unlikely that I won’t be able to flow your speech. I do, however, think you should slow down when reading topicality arguments, procedurals and important texts (plans, alternatives, permutations, etc.). I like things to be specific which means copying down an accurate text is pretty important to me. If I can’t I will let you know. Dress however you want. I honestly do not care what you’re wearing or what you look like. Don’t be an asshole. This doesn’t mean you can’t clown on other teams or debate intensely in important rounds (I’d actually prefer that you did). What it does mean is that you probably shouldn’t run up the score on or totally embarrass obviously weaker teams for no reason. It also means you shouldn’t make racist / homophobic / sexist / whateverist comments.
Also, rights malthus makes sense to me. Take from that what you will.
I suppose that’s it. Debate hard, debate smart, and have fun. If you have any further questions feel free to let me know!
Hi! My name is Cory Freivogel. I did four years of policy debate in high school in the Chicago area. After that, I spent four years doing Lincoln Douglas and Parliamentary debate at McKendree University. I’m currently the assistant coach there.
I will preface this philosophy in the way that most people do - I think you should debate however you debate best in front of me. That being said, I obviously have certain biases and I think you should be familiar with them.
Some general notes….
1. I think debate is first and foremost a game. I think you should do whatever it takes to win that game, and I respect people who play the game with a lot of heart and lot of intensity.
2. I like people who do work. This doesn‘t mean that I won‘t vote for lazy, trite strategies - I have no problem doing that. It just means I respect people who put in extra effort to develop or update sweet arguments.
3. I like people that talk pretty. I certainly don’t think you should ever sacrifice strategy and execution for eloquence, but if you can give a smart speech that’s funny and engaging it will bode well for you. Also, don’t try to be funny if you’re not.
4. Don’t dismiss defensive arguments. Of course I think you should be making a wide variety of offensive arguments, but do not assume you’ll be fine by saying that 9 smart, defensive answers to your affirmative are just defense.
DISADVANTAGES
I like these arguments a lot. Running well-researched disadvantages with a diverse set of link arguments and huge probable impacts is the easiest way into my heart. Generic disadvantages like politics, business confidence, etc. are fine as well so long as they’re specifically tailored to the affirmative and properly executed.
Similarly, I think smart negatives (and affirmatives as well) will do a great deal of work comparing impacts. If you do not do this I will make my own determination about the probability and magnitude of a disadvantage’s impact. I am also probably more concerned about probability than some other judges may be. I am not often impressed by massive impacts that are highly improbable and under-explained. Phrases like “even a 1% risk of our impact outweighs the entire risk of the aff” are typically code for “our impact is absurd and our disadvantage barely links.”
COUNTER PLANS
These arguments are sweet as well. I typically err negative on arguments like PIC’s bad, conditionality bad, etc. I will vote on these arguments, but it will be an uphill battle. The argument that I should reject the argument rather than the team is usually a winner. I think condition, consultation and other silly process counter plans are of questionable legitimacy and I can definitely be more persuaded to drop teams on theory if they’re extending these arguments. That being said I like counter plans of all shapes and sizes and think that if you aren’t reading one or straight turning the affirmative, then you’re probably in trouble.
KRITIKS
I am not as hostile to these arguments as most people probably think I am. I am, however, probably as unlikely to understand these arguments as most people think I am. I have not and probably will not ever read any traditional or post-modern philosophy unless someone requires me to do so. I’m not trying to dog on anyone that does, but it’s just not my thang. This is mainly meant as a word of caution. If you run the kritik I will listen, flow and do my best to make a fair decision. But, I am not the best critic for you. If you somehow find me in the back of the room and you have nothing but your criticism, it will serve you well to slow down and eliminate all the jargon you imagine I may be familiar with.
That being said, if you’re an affirmative answering these arguments do not assume I will let you get away with answering kritiks poorly. If you mischaracterize the criticism, concede framework arguments, or rely on defense then I’ll probably notice and you’ll lose.
TOPICALITY
I like good topicality debates a lot. If you are affirmative, then you need to meet the interpretation or you need a counter interpretation. Absent one of those things, you will probably lose. If you are going for or answering topicality you should be comparing standards and voting issues in the same way that you compare impacts. If you do not compare standards, it will make it very difficult for me to make a good decision and it will be bad for everyone. I am also more persuaded by arguments about ground than limits. I could care less if your interpretation “explodes the topic” given that the topic will only exist once and you don’t have to do any research in the future.
ASPEC / OSPEC / FSPEC / BILL NUMBER SPEC / COMMITTEE ORIGINATION SPEC / BLAH BLAH SPEC….
These arguments are really not my cup of tea. This is mostly because I don’t like giant pieces of shit in my tea. I understand the strategic utility of introducing these arguments in the LOC, but I cannot understand why one would choose to extend them in the MO unless there was some incredible example of abuse. It is difficult for me to imagine giving any higher than a 27 to even the most persuasive extension of a generic specification argument.
THE CASE
People forget about the case all the time. That makes me sad because I love a good case debate. If you’re the LOC and you don’t have an incredible counter plan, then you should be putting a lot of offense on the case. Similarly, the MG should be extending and utilizing the case throughout his or her speech. It frustrates me to no end when affirmative teams assume they can entirely ignore the case until the PMR when it suddenly becomes the focus of the debate. Personally, I think you should have to extend the affirmative throughout the debate.
POINTS OF ORDER
I keep a pretty decent flow and think I can detect new arguments on my own. That being said, they are allowed by the rules and if you think there is a particularly egregious example of an abusive new argument feel free to call it. However, if I know an argument is new I will protect the opposite team regardless of whether or not you say it's new. If you call a bunch of unnecessary points of order on teams just to disrupt their speech or be funny or whatever I will be very unhappy. I hated when teams did that when I debated and I imagine I will hate it even more as a judge. Don't do it.
POINTS OF INFORMATION
I think as a general rule you should probably accept two of these per speech. I could pretty easily be persuaded to pull the trigger on a "they didn't take any questions" type of procedural. Also, no means no. If someone won't take your question don't yell that question or jump around waving your hands like an idiot or yelling "Please!! Just one!!" The only exceptions to this are in instances when you need to know the status of a counterplan or to have a text repeated / handed to you. I don't think you should have to raise your hand to ask for those things. Maybe there is no legitimate justification for that, but that just happens to be what I think.
OTHER THINGS…
You can go as fast you like so long as you’re clear. I went pretty quick when I debated and its unlikely that I won’t be able to flow your speech. I do, however, think you should slow down when reading topicality arguments, procedurals and important texts (plans, alternatives, permutations, etc.). I like things to be specific which means copying down an accurate text is pretty important to me. If I can’t I will let you know. Dress however you want. I honestly do not care what you’re wearing or what you look like. Don’t be an asshole. This doesn’t mean you can’t clown on other teams or debate intensely in important rounds (I’d actually prefer that you did). What it does mean is that you probably shouldn’t run up the score on or totally embarrass obviously weaker teams for no reason. It also means you shouldn’t make racist / homophobic / sexist / whateverist comments.
Also, rights malthus makes sense to me. Take from that what you will.
I suppose that’s it. Debate hard, debate smart, and have fun. If you have any further questions feel free to let me know!