In the world of software development, one of the current buzz phrases is
"minimum viable product". The idea is that in order to be able to
launch quickly, the first version of a product should contain the
smallest amount of functionality that might actually be useful.
This is an excerpt from my March 12, 2012 post. I've been missing automated poker hand histories for so long, I've decided it's time to bite the bullet and record some of the hand data manually. Since it won't be possible to record every detail manually, I need to decide what the minimum viable poker hand data are for me. Of course, I need to record my hole cards for every hand I've been dealt; that's a given. It's also imperative for me to record whether I won the hand or not. Other than these two vital details, I need to figure out what other data I might want, using a cost benefit analysis. The cost is the time and effort it would take to record each additional datum, and the benefit is whether having the datum will be able to help me improve my game. I'll give the following a shot:
1. my hole cards
2. whether I saw the flop
3. whether the hand was an all in, a call in, a fall in, or none of these
4. whether I won the hand
style flavor buy_in entry players entries paid place winnings
MTT NLHE 44000 6000 9 346 81 149 0
delta: $-50,000
2025 balance: $-1,184,000
2025 blue distance: $1,184,000
balance: $15,113,303
MTT NLHE ITM pct: 41.45 (1294 of 3122)