The remote programming seems like a novelty aimed at hobbyists. If I have a deployment of remote devices, large or small, iterating on code on a device in the field is a recipe for disaster. How will you track the different versions of code on the various devices you have changed individually? If you need to directly change the code on a field device, doesn't that imply that you are unsure that the changes will work?
If the code needs to change, that is much safer to do in a controlled, low risk, nonproduction environment, where you will very likely have development hardware that has been optimized for ease of development/debugging. Once changes are tested and otherwise validated, an over the air update process would be used to send that new firmware image to the device. This way, your devices all can be on a single version of the firmware, meaning you can scale the deployment of that update to 10, then 100, then 1000 devices, etc.
If the code needs to change, that is much safer to do in a controlled, low risk, nonproduction environment, where you will very likely have development hardware that has been optimized for ease of development/debugging. Once changes are tested and otherwise validated, an over the air update process would be used to send that new firmware image to the device. This way, your devices all can be on a single version of the firmware, meaning you can scale the deployment of that update to 10, then 100, then 1000 devices, etc.