> Instead of pushing the external, side-effecting thing down the stack, I put it up the stack and call the logic that generates the data for it from there. I'v

> Instead of pushing the external, side-effecting thing down the stack, I put it up the stack and call the logic that generates the data for it from there. I've never seen Go code that does anything else. That's not to say it doesn't exist, but it's seemingly not the norm amongst Go developers (probably exactly for the reasons you describe). That doesn't address what the parent is talking about, though. You have the exact same problem spoken of no matter where in the stack you put it.