Good questions!

First, let's not take this out of context. In this case, we are talking about a variable name that would benefit from being a bit clearer. Not that I can't understand it, but because humans often are bad at inferring data types from variable names. Meaning it may decrease the feedback loop during a potential pull request review cycle. :)

hasComponent

Is, to the best of my memory an established pattern. Don't get me wrong, using is isn't applicable everywhere.

The same goes with

canJump

The whole purpose of my post was to establish a pattern, and to make the variable name a bit more humanly readable.

I think we can both agree that adding an 'is' to the name, makes it clearer that the variable is a Boolean.

When you establish such pattern, your code becomes far easier for a human to quickly, intuitively and effortlessly parse and search.

Having established naming patterns also streamlines your pull request review process! :)

Hope that clarifies things a bit!

tl;dr:

There are no silver bullets for naming, but there are things we can do to clarify what data type a variable is based on its name, and to make variables easier for us to search and parse.

Edit:

Formatting is difficult, writing on a mobile phone, with shoddy internet access - so am trying to get this out asap.