Two Plus Two Newer Archives  

Go Back   Two Plus Two Newer Archives > Limit Texas Hold'em > Small Stakes Shorthanded
FAQ Community Calendar Today's Posts Search

Reply
 
Thread Tools Display Modes
  #1  
Old 10-25-2007, 04:51 AM
SteveL91 SteveL91 is offline
Senior Member
 
Join Date: Jan 2005
Posts: 774
Default Re: Flop blind defense spot

[ QUOTE ]
Well this is a very standard 3-bet preflop, so you shouldn't really have a decision like this.

[/ QUOTE ]

I don't think it is and I don't think it should be. If you're regularly 3betting this hand from the BB against a button opener, you're going to get tortured by anyone competent. You're either going to be in far more capped pots, or flat-out abused post-flop when you completely miss and his hand range hasn't been defined in any appreciable way because he just called PF. Either way, you're left in a decent sized to big pot, where you're going to end up making more mistakes than the other guy.

If it shows a profit for you, then maybe it works for you and you've found a way to make it profitable. But, I think you're going to find it's a crappy spot more often than not.

To address the OP: I used to be of the mindset that a c/r here was rather pointless, since you're at least getting called down by better hands while folding out worse hands. However, I'm starting to think there's more value in getting people to fold their 6+ out hands that they would play differently if they knew your holding.

Basically, if it's someone who plays honestly and you have control over, I don't see a problem with a more aggressive line; against someone who just won't let you get off that easily, I think my default would be to c/c if I wanted to showdown UI. But, this is a spot that I'm still debating myself.
Reply With Quote
  #2  
Old 10-25-2007, 06:16 AM
lippy lippy is offline
Senior Member
 
Join Date: May 2006
Location: i ain\'t got my taco
Posts: 3,905
Default Re: Flop blind defense spot

[ QUOTE ]
[ QUOTE ]
Well this is a very standard 3-bet preflop, so you shouldn't really have a decision like this.

[/ QUOTE ]

I don't think it is and I don't think it should be. If you're regularly 3betting this hand from the BB against a button opener, you're going to get tortured by anyone competent. You're either going to be in far more capped pots, or flat-out abused post-flop when you completely miss and his hand range hasn't been defined in any appreciable way because he just called PF. Either way, you're left in a decent sized to big pot, where you're going to end up making more mistakes than the other guy.

If it shows a profit for you, then maybe it works for you and you've found a way to make it profitable. But, I think you're going to find it's a crappy spot more often than not.

To address the OP: I used to be of the mindset that a c/r here was rather pointless, since you're at least getting called down by better hands while folding out worse hands. However, I'm starting to think there's more value in getting people to fold their 6+ out hands that they would play differently if they knew your holding.

Basically, if it's someone who plays honestly and you have control over, I don't see a problem with a more aggressive line; against someone who just won't let you get off that easily, I think my default would be to c/c if I wanted to showdown UI. But, this is a spot that I'm still debating myself.

[/ QUOTE ]

It's like you think I would only raise A9o from the BB. Yeah, I raise Aces as well...

Stox on this type of situation, "when defending from the big blind, you should often three-bet hands that figure to be best. Alternately, you can call and check raise a lot of flops with hands that benefit from getting folds, specifically smaller pairs and ace-high hands."
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 08:36 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.