It's not critical either way, but my personal preference has been to avoid having standalone functions scattered throughout a codebase. Over time they can accumulate, and people can forget what exists when it comes time to reuse something. I don't think it impacts understanding, because assuming you have a good editor, you can see the docstring by placing your cursor on the call. But again, it is not a critical issue at this point. In the distant future, it might be more reasonable to have a `utils/deco.py`, `utils/numpy_helpers.py`, and `utils/inspect_helpers.py` (for these three functions, respectively), when there are enough utilities to warrant such granularity. I am against having a catch-all file, contrary to what I did here, but it can still assist in transitioning into the later stages.