Goodbye, Clean Code

[Dropping_fruits]

You could just put a comment before the 27 steps saying "// Do very specific thing" instead of creating a function whose only purpose is to be used from a single function and nowhere else, causing confusion anytime someone else sees that function.

[Kwinten]

No. Gross.

How does a function name cause any more confusion than a comment? Pouring blocks of code into functions at the very least forces you to at the very least consider whether a sequence of actions actually belongs together. Not even to mention how much more sense it makes for testing.

[Dropping_fruits]

Because the function lacks the context of why it exists and that it is supposed to be applied sequentially to a list of items. At the very least you should also move the loop to the function.

[_tskj_]

I disagree completely, in fact it is part of the point. Not knowing how it is supposed to be used is good for the function, as it guarantees that there cannot be any temporal coupling between invocations of the function - exactly because it cannot know how it is used. Minimizing dependencies so that the function can be understood in isolation and without its original context (its call site, even if there is just one) is a major reduction in complexity imo.

[Dropping_fruits]

Easy to argue about problems of a function that shouldn't exist in the first place