I have had the same experience, although I've only been out of school for two years. So far my daily work stream has me doing ssh to a Linux box and then doing my work there. All the CI/CD, version control, building code, and storing the code is done remotely.
So far it's been great (again, I've never had an alternative) and the power of virtualization has really come in handy. A couple of times in the past I accidentally borked my Linux box and started to figure out how to fix it, but then I had my d'oh moment: just scrap this one and get another!
There's no "it works on my machine" and most importantly, I can work from anywhere, with a stable internet connection (even using a phone to do USB tethering worked fine), from a Mac, a Chromebook, windows, whatever computer.
One caveat is that I program backends in C++ so a lot of the issues mentioned in the article don't really apply to me. Regardless, it's been great!
So far it's been great (again, I've never had an alternative) and the power of virtualization has really come in handy. A couple of times in the past I accidentally borked my Linux box and started to figure out how to fix it, but then I had my d'oh moment: just scrap this one and get another!
There's no "it works on my machine" and most importantly, I can work from anywhere, with a stable internet connection (even using a phone to do USB tethering worked fine), from a Mac, a Chromebook, windows, whatever computer.
One caveat is that I program backends in C++ so a lot of the issues mentioned in the article don't really apply to me. Regardless, it's been great!