What size Pi? Memory? Disk storage? If, for example, you get a 8 GB instead of 4 GB, you can go crazy with options. You could keep all your code on your PC then share the code directory to the Pi using NFS or Samba or whatever. You now have the same code on both machines. The code could be on the Pi then shared back to the PC. You can edit and backup on either machine. Your editing can be on the Pi using screen sharing.
My main reason for keeping code on my notebook is the code runs on both. I test on the notebook then compile on the Pi using the same code. None of my code uses GPIO pins. If it was GPIO stuff, I would plug a screen into the Pi, edit and test there, then backup on the notebook using the Pi directory shared back to the notebook.
My Pi 5 has everything on an NVMe SSD plugged in via PCIe 3. It is essentially the same speed as my notebook. I would minimize Pi compiles and testing if it was not Pi 5 with PCIe 3 NVMe.
Using Git to share code would be a better solution if your network connection is not always available or unreliable. You could edit on your notebook down at the beach then on yur return to base, update the code on the Pi from Git.
My main reason for keeping code on my notebook is the code runs on both. I test on the notebook then compile on the Pi using the same code. None of my code uses GPIO pins. If it was GPIO stuff, I would plug a screen into the Pi, edit and test there, then backup on the notebook using the Pi directory shared back to the notebook.
My Pi 5 has everything on an NVMe SSD plugged in via PCIe 3. It is essentially the same speed as my notebook. I would minimize Pi compiles and testing if it was not Pi 5 with PCIe 3 NVMe.
Using Git to share code would be a better solution if your network connection is not always available or unreliable. You could edit on your notebook down at the beach then on yur return to base, update the code on the Pi from Git.
Statistics: Posted by peterlite — Fri Aug 01, 2025 10:26 am