Clean and simple hot-reloading on uninterrupted go applications

When I read hot reload for a language, I'd expect it to notice changes to the source of the program and hot reload it.

This seems to not be doing that, rather reloading config and having a sequence of actions happen after the change in a defined order.