This walkthrough is planned but not published yet. The transcript below covers the same material if you would rather read it now.
What @eugo.hpc.distribute actually changes about a function, and why the call site stays clean.
Decorating a function with `eugo.hpc.distribute` changes what calling it does. Instead of running the body immediately and returning a value, the call schedules the work somewhere on the cluster and returns a future: a handle to a result that does not exist yet. Your code keeps running. This is why the decorator matters at the definition site rather than every call site: the calls themselves look like ordinary Python.