Not my money any more: Lessons from poker (2010)
tidyfirst.substack.com
Not my money any more: Lessons from poker (2010)
1–10 of 18 posts
Re: Not my money any more: Lessons from poker (2010)
#2Re: Not my money any more: Lessons from poker (2010)
#3Re: Not my money any more: Lessons from poker (2010)
#4Time is not like money in that no time that elapses is ever yours to get back. Whereas sometimes money that leaves your hands is actually still yours.
Giving up on a refactoring because of some failed tests could be wasteful.
How much time you put into the refactoring already should enter into your decision making because if you throw it away, you may have to put in a comparable amount of time to redo the job.
If you've sprayed 15 coats of lacquer on a piano and a fly lands into your 16th one, do you strip it and start again, or just sand out the blemish and keep going? What if it's half a coat on a ukulele?
Re: Not my money any more: Lessons from poker (2010)
#5Re: Not my money any more: Lessons from poker (2010)
#6Anyone else notice the mangled fingers in the AI generated image up top?
Re: Not my money any more: Lessons from poker (2010)
#7Yes, I have to always remember the sink cost fallacy… but remember it can also motivate you to continue on when times are tough so that you do not give up
Re: Not my money any more: Lessons from poker (2010)
#8Re: Not my money any more: Lessons from poker (2010)
#9Re: Not my money any more: Lessons from poker (2010)
#10This person needs to make small git commits as they refactor, and use git bisect to find which one broke the test, then fix it and squash that fix into that commit with interactive rebase ... Time is not like money in that no time that elapses is ever yours to get back. Whereas sometimes money that leaves your hands is actually still yours. Giving up on a refactoring because of some failed tests could be wasteful. Ho…
And "this person" is https://en.wikipedia.org/wiki/Kent_Beck btw.