remote-code.md

@@ -57,7 +57,11 @@ The figure below shows an example where a local project found in `~/Documents/co
 
 **IMPORTANT:** the Python virtualenv does *not* need to be in the same folder as your project. In fact, in many cases it could be better to have them in separate folders, for the reasons explained below. For instance, on `icaro.polito.it`, it may be convenient to have your virtualenv in `/home` and your project in `/space`
 
-Lastly, click "Finish" on the dialog shown in Figure 2 to complete the setup of your remote interpreter.
+#### Finish the Interpreter Setup
+
+Lastly, click "Finish" on the dialog shown in Figure 2 to complete the setup of your remote interpreter. You can now run (and debug) your Python code running on the server directly from your local machine, without the need of a permanent GUI session.
+
+Notice that remote execution is interrupted if you lose your internet connection to the server. So, for long-running programs, a permanent shell could still be necessary (see ["Connecting to the Servers"](/connection)).  However, this mechanism is very convenient for development, short tests, debugging, etc.
 
 #### Accessing Remote Files