Really? There's a perfectly good example in the article. RunFewerTimesSlowerAndSimplerAlgorithmAfterConsideringTradeOffs() That's a horrible way to name a

Really? There's a perfectly good example in the article. RunFewerTimesSlowerAndSimplerAlgorithmAfterConsideringTradeOffs() That's a horrible way to name a function. Function names should be short, punchy, and unambiguous. They should create a simplified abstract narrative, and all the details should be put into the docstring, so that they can be easily accessible without having to (a) be squashed into an identifier, or (b) be repeated every time you want to call the function.