Two Plus Two Newer Archives  

Go Back   Two Plus Two Newer Archives > PL/NL Texas Hold'em > Full Ring
FAQ Community Calendar Today's Posts Search

Reply
 
Thread Tools Display Modes
  #11  
Old 11-27-2007, 08:18 PM
Johnes Benjamin Johnes Benjamin is offline
Senior Member
 
Join Date: Mar 2007
Location: 3rd & Delaware
Posts: 848
Default Re: NL25: AA. comments please

You can't let them get to the flop so cheap.
If they have a hand that they are going to call an allin with on the flop, they will usually have either improved to better than 1pair, or they had a hand that they would have called allin preflop with anyway.
Reply With Quote
  #12  
Old 11-27-2007, 08:22 PM
AlexB182 AlexB182 is offline
Senior Member
 
Join Date: Dec 2006
Posts: 1,235
Default Re: NL25: AA. comments please

[ QUOTE ]
[ QUOTE ]
In ordinary circumstances I'm going to pop in a raise when the Btn raises for the 2nd time, fairly sure that one of them has a big pair.

[/ QUOTE ]

In "ordinary circumstances" you need to raising AA from UTG and go from there. Occasionally, limp reraising it might be fine, but you need to actually reraise when you get the chance.

[/ QUOTE ]

LOL. Funny AND true. This is a great position to be in, 2 guys like their hands and you have aces. Seriously, raise here.
Reply With Quote
  #13  
Old 11-27-2007, 08:26 PM
coordi coordi is offline
Senior Member
 
Join Date: May 2007
Location: running bad, playing bad
Posts: 1,622
Default Re: NL25: AA. comments please

[ QUOTE ]
Just raise preflop. There is no reason to be tricky at these stakes.

[/ QUOTE ]

QFT

By the time BB bets 3.20 or whatever you should just shove because they obviously aren't folding, and you obviously aren't repping AA really...
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 01:13 AM.


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