Two Plus Two Older Archives  

Go Back   Two Plus Two Older Archives > Limit Texas Hold'em > Micro-Limits
FAQ Community Calendar Today's Posts Search

Reply
 
Thread Tools Display Modes
  #31  
Old 10-05-2005, 04:25 PM
SlantNGo SlantNGo is offline
Senior Member
 
Join Date: Jun 2004
Posts: 133
Default Re: Pocket JJ

I call this flop even if we know BB has the Q a majority of the time, as long as Button isn't the type to raise here often. I'll give ourselves 3 outs right now... when the action gets to you, the pot is 12 SB. I estimate the expected pot size on the turn to be 15 SB. Hence, using DIPO:

Good Number: 15 * 3 = 45
Bad Number: 47 - 3 = 44

This is a call, and I haven't even accounted for the chance that we're ahead right now, which is often enough to tip a marginal fold into a marginal call. Then, fold the turn unimproved.

Against a villain who will bet out with a larger range, the turn play gets more interesting. We could be ahead of the flop quite often, but there are many cards that we want to dodge on the turn (Aces and clubs). If a bad card comes on the turn, I'll fold. If I pick up a straight draw, I'll call.

However, if the turn brings a blank, i.e. non-club 2 to 8, I would strongly consider raising the turn for a free showdown.
Reply With Quote
  #32  
Old 10-05-2005, 04:29 PM
sean c sean c is offline
Senior Member
 
Join Date: Jan 2005
Posts: 391
Default Re: Pocket JJ

[ QUOTE ]
you may do that, and that would classify as an aggressive read. you are betting out on a blank turn as well? that's why i said if 3-bet and bet into on the turn without that read, i'd fold.

[/ QUOTE ]

No i would not bet a turn blank without enough equity to do so. Missed the bet the turn part.
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 03:28 AM.


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