I thought the same thing as well. For every best practice there is a counter-example. In the case of a simple procedural task that doesn't have any independen

I thought the same thing as well. For every best practice there is a counter-example. In the case of a simple procedural task that doesn't have any independently executable pieces, the value of splitting it up into sub-methods is debatable. All else being equal, it sometimes comes down to whether the sub-tasks have an intuitive mapping to English, if they don't map well to English or there are cross-cutting concerns or ambiguities underlying the names of the methods then I'd say it's a net loss to readability and better to just have one big hairy method.