Quote:
Originally Posted by browni3141
People are saying these are standard defends because they are. Two sources I have found in a brief search recommend defending these hands. (Applications of NLHE, Pokersnowie) You may claim that these are outdated or inaccurate or whatever, but I challenge you to find a source which recommends folding QTs to 3-bet CO vs. BB, without the stipulation that BB is very tight or passive.
This was important enough to quote for it's own response. I'm not sure if you have read Applications of NLHE or not, but the book is designed for GTO play vs. "perfect" opponents in 6-max style games.
His section on defending against 3!'s (p.69) with hands like KTs, J9s etc has fairly strict assumptions:
1. You are opening a 40% range from the BTN in a 6-max game (not CO in a live full-ring game such as this hand)
2. You are opening for 2.5x BB
3. Villain is 3! to 9.5 BB's
4. Villain is defending wide enough that his worst hand is losing 5.5 BB's on average
(good luck creating a proof of concept for this one)
5. You are playing with 100 BB stacks and are going to make super loose hero calls and super marginal near 0EV bluffs for your stack on the river.
I think it's important we don't miss the forest for the trees here. The game and theory Janda is describing is an apples-to-oranges comparison to a typical live 2/5 game. The overarching theme that gets repeated ad nauseam on this forum is
"exploitable poker trumps balanced/optimal poker 99% of the time.
Is it more likely that this villain is some online 6-max wizard with perfectly balanced ranges and frequencies from every position, or rather he is just 3!ing a fairly linear range from OOP vs. your CO open
(not the BTN which is another fairly significant flaw to overlook!).
I think it's a leak to defend light here at this stack depth/SPR vs. my range estimate for villain. You don't. Who knows who is correct. But what I feel pretty confident about is misinterpreting something you read in a book and not applying it correctly is likely massively -EV/leaky.