I feel bad saying this since the author is very excited and clearly put a lot of work into the "satisfying" checkbox. But...
This is why we can't have nice software UIs.
The process here seems to be to take a simple, utilitarian UI element -- a means to an end -- and turn it into the center of attention:
1. Make it big.
2. Make it flashy.
3. Make it slow.
4. Make it loud.
5. Make it literally vibrate.
These are not the characteristics of a satisfying tool; they are the characteristics of a toy for toddlers. On a deeper level, this is the sort of thinking that comes from looking at the interface instead of past it. That is an understandable perspective for a designer, but indulging in that perspective results in interfaces that just get in the way.
It's also a very artificial approach. A "satisfying ka-thunk", in particular, it satisfying in part because it's the sounds of a weighty metal mechanism operating smoothly. "Weighty", "metal", and "smoothly" are all things we associate with high quality. Aping some superficial indicators of high quality is usually not very satisfying on its own.