I think there's a hidden assumption that the author didn't expose. > when I have a relatively small and simple chunk of code that needs to run every once in a

I think there's a hidden assumption that the author didn't expose. > when I have a relatively small and simple chunk of code that needs to run every once in a while. I think "run every once in a while" actually means stable requirements. I think the number of executions per time is irrelevant. Being stable is the important thing. My theory is that "run every once in a while" is substituting stable requirements because that's what I also see in organizations. What is execute a lot usually has an higher importance for business which also translates to unstable requirements.