No thanks, that's even worse. It's honest, but that doesn't make it a good idea. I like to do one thing at a time, not jump around like a wild horse. Turns out optimizing for not jumping around too much also makes programs simpler overall.
I've recently cleaned up some code of this kind. Defines objects with unsuitable lifetime and tries to be smart about reusing work instead of planning out in which order to do things in the first place. While the actual task was not difficult, the code was incomprehensible, to state it in a diplomatic way.
And if you think consciously about the intermediate data you probably can use it for a whole lot of other things!
In Haskell, unexpected memory expansions and duplication of work can happen. And these problems are not nice to debug.
I might be generalizing too much, though. Maybe you're talking about short-lived web applications that never see a large amount of data, or something like that.