Read this on mobile and the identifier longWindedNameThatYouCantReallyReadBTWProgrammersDoThatALotToo overflowed into the margins - I regard this not as a bug but a feature which helped make the author’s point :-)
We use this technique as a guide in our company. If someone (knowledgable) would ask "What does this method call do?" and the method name does not answer that, your PR doesn't go in the master.
E.g. getString(path) for loadConnectionStringFromDisk(configFilePath), tryConnect(30) for testSqlConnection(timeoutInSec), even the reader now knows what happens here and what input is expected.
I never understood nor understand people who nest their inner loops in an entangled mess of hardly distinguishable digits, which is error prone.
Same for method names.
I try to use speaking out loud to some of my methods: What do you do? And if the answer is getValue I believe it needs renaming.