WFH is not an impossible dream.
Everyone knows that for a long time, the embedded industry was limited to supplying Windows-only toolchains due to interference from those damn chip vendors. That is why the ThinkPad was the "standard" device in this field for so long. It was only recently that it began supporting macOS and Linux. In this situation, I came up with an idea of my own. It was this:
"Since embedded systems have to interface chips with computers and connect measuring instruments to pins anyway, why not just connect the development environment, JTAG, and oscilloscope to a server and access them remotely?"
I know this sounds crazy. However, before you refute it, please listen. We can self-host VS Code on a server using Docker. Through this, we can access it via a web browser and complete the compilation process. Theoretically, using tools like Moonlight, we can run KiCad, FreeCad, CubeMX, and others at smoother refresh rates than VNC (I really wish ST would handle pin mapping within VS Code, just like Nordic Semiconductor does). While instrumentation might seem like a tricky issue, most instruments are accessible via LXI or web pages; all you have to do is set up debugging pins on a board or breadboard beforehand and connect a logic analyzer or oscilloscope. In that case, all we need is a device with a keyboard that supports Tailscale, and we are ready to perform WFH. I wonder why we are unable to work from home despite having these means in place.