I've noticed this eager refactoring. The flip side of this is that (and in this particular case), similar structures (like the spawning of children) end up in different methods, and it's harder to see the resemblance.

Comments can devolve into lies, but I prefer something more akin to literate programming. I vehemently disagree that comments reflect any clarity in code. Having these methods spread out leads to long and ugly method names and more state held in the object than is necessary. I'd rather have comments tell a story rather than have method names do it.

One feature of splitting these out that I find tiresome is having to jump back and forth between different methods to see the flow through a single atom (like `run`). In its longer form, it easily fits in a single screen.

We may disagree, but we also cannot keep waffling on this point. While by that article's metric this method is 'enormous', it stands fine as a single cohesive unit.

Perhaps someone else would like to weigh in on this point.