When I was a kid, I really enjoyed Cap’n Crunch cereal. I don’t know what it was about it that I enjoyed (these days I avoid food with added sugar) but it was worth the palate shredding at the time. Once in a while we’d get the variety with Crunchberries. This was a rare enough event that I would carefully eat around the Crunchberries leaving them behind so that at the end I had a bowl of Crunchberries in milk that was slowly turning pink. I did the same thing with Lucky Charms or any other cereal that had special kernels in it so I could enjoy them all at once with no effort.
To that end, I just submitted this PR to my project Binding Tools for Swift. It fixes a typo in an issue opened more than a month ago after one of my peers spotted it in a previous PR. It’s a no brainer fix – rename the method and Visual Studio takes care of the rest.
Why did I wait more than a month to do fix this? Two reasons: 1. I was hoping that the “good first issue” would entice someone else to have a go at fixing it to get their feet wet on the code base and 2. for the past month, I’ve been working on mostly challenging issues. Sometimes it’s nice to get work done, but still take a break.
This is the same as setting aside the Crunchberries. It’s a way of setting aside a reward. Sometimes the reward is a small one like this. Other times, it’s a refactoring that you know will make so many things better. Current Steve likes to set up nice things for Future Steve so that when Future Steve becomes Current Steve, he’ll be more likely to be forgiving of Past Steve’s mistakes.
Do you find ways of doing that? If so what?