Utah Senate 2006: Ken Jennings (user search)
       |           

Welcome, Guest. Please login or register.
Did you miss your activation email?
April 28, 2024, 01:30:45 AM
News: Election Simulator 2.0 Released. Senate/Gubernatorial maps, proportional electoral votes, and more - Read more

  Talk Elections
  Presidential Elections - Analysis and Discussion
  Election What-ifs?
  Past Election What-ifs (US) (Moderator: Dereich)
  Utah Senate 2006: Ken Jennings (search mode)
Pages: [1]
Author Topic: Utah Senate 2006: Ken Jennings  (Read 805 times)
Alben Barkley
KYWildman
Atlas Icon
*****
Posts: 19,282
United States


Political Matrix
E: -2.97, S: -5.74

P P
« on: June 07, 2020, 03:16:08 PM »

Well, Jennings would be able to self-fund (to some extent), and I'm reasonably confident he would be able to fundraise.

That said, it would be very difficult to beat Hatch, even in a D wave.

Also, didn't Jennings live in Washington by 2006?

Orrin Hatch (R) 59%
Ken Jennings (D) 39%

I hate to say this as a massive Jeopardy! fan because Ken Jennings is literally my deity, but considering Hatch won reelection by over 30 points in real life, I don't see how a Democrat whose sole claim to notoriety was winning millions on Jeopardy! is gonna close that margin of victory.

Come on, the only reason Ken won the greatest of all time tournament was because he kept beating James Holzhauer to the daily doubles.

Actually he ultimately won because James blew the Final Jeopardy — surprising since James almost never lost the Final Jeopardy while Ken was weaker at them. Also James’s strategy was all about having a fast trigger finger and hitting those daily doubles before anyone else could, then betting big. That was not Ken’s strategy before, but he adjusted brilliantly. Let’s face it, Ken beat him at his own game.
Logged
Pages: [1]  
Jump to:  


Login with username, password and session length

Terms of Service - DMCA Agent and Policy - Privacy Policy and Cookies

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines

Page created in 0.021 seconds with 13 queries.