I vehemently dislike coding directly on my workstation and do all of my development in remote VMs via SSH, when possible. My work MBP is a glorified SSH terminal with a web browser. I got my start in the industry with remote SysAdmin stuff so, it feels pretty natural.
For an IDE, I use Neovim, currently with a plugin distribution - Neovim because I got used to the vim syntax as a SysAdmin and the distribution because I can’t justify sinking more time into tuning my env for a bit but am intending to scrap it all around the holidays or so.
Most of my work is in Go or Python. At home, it’s a mix of CircuitPython, C, and I’m picking up some Rust (mainly embedded for C and Rust). Will be starting to learn Verilog this weekend.
For Go and Python, I tend to lean towards a TDD approach, even if it gets a bit derided by coding streamers.
My workflow tends to be:
Prototype desired functionality to get at least individual parts working.
Start from scratch and rough out any classes/structs and test suite boilerplate.
Start the red->green->refactor loop, giving extra granularity to parts of code that I am less confident in.
Once all intended functionality is implemented, run manual tests (I generally develop tools).
Fix bugs that unit tests failed to prevent or I failed to anticipate.
Repeat 4 and 5 until acceptable.
Prepare commit.
Push commit and receive failure because I haven’t fully configured my formatters to clean trailing whitespace and VT100-compatible line lengths.
Push commit again and send for code review.
Currently, my build automation is kinda in CMake. Really, the Makefile is just calling a build in a docker container.
For C, Rust, and Verilog, I’m not yet familiar enough to have yet established workflows.
ETA: I think I just got the same FPGA as you! Xilinx Zync-7020 (Digilent Arty Z7-20).