I'm nitpicking a bit on code naming...

Today’s review had a final note: I’m nitpicking a bit on code naming. The approaches you take are good, but naming is hard:

There are only two hard things in Computer Science: cache invalidation and naming things.

(see here a list of variations on these two hard problem ‘jokes’ in Computer Science)

I enjoy the ruby programming language because you can get a long way just assuming things. They might say, never assume things, because a lot of things are chaos, but I prefer to work from assuming things, and if it doesn’t match to my assumption choose:

1. fixing the assumption (perhaps by making the method name more clear)
2. make it so that what I assumed to be working works (and I never ever have to think about or bother by it anymore)

… and/or maybe, I am just wrong and I should level up my understanding of things. We all have our internal models of how things work, sometimes they are wrong and these internal models need some adjustments :)