> I'm working against the system instead of with it, and someone else is trying to boss me around.
This resonates with me a lot.
I started my first "proper" job this year, and the dev env we use is pretty run-off-the-mill: docker, TS, AWS...
But there is one big issue and that is that I had to switch to Windows a while back for driver reasons (looking at you, Dell and Intel) and this is the first time in over 9 year that I have used Windows proper. Not a fault of my employer I should add.
In academia, and at home, I have been running Linux for ~14 years by now, so I had skipped Windows 8 and this is my first contact with Windows 10. And while I appreciate how much more stable this system is than my XP from way back when, it feels horrible, and pretty much for the reasons described here.
It's not that Linux was always smooth sailing, or that it was easy, or user friendly in the conventional sense. But there is a huge difference in my relationship to the system:
On Linux (and generally with FOSS software) whenever I hit a problem, if something didn't work, I could be sure that it was not there because someone didn't want me to be able to do it like that. It was always a lack of resources or insight, or both. And people and systems in FOSS are built to enable me to change things.
Working on windows, I tried setting up my PC in the way described in the article. Halfway through I realized that I was just fighting against the system, trying to make it do something it didn't want.
Needless to say, MacOS is not an alternative to Windows for me. They're both dead to me. Lesson learned, gonna vote with my money from now on. I started by ordering an MNT Reform for my personal use (not speedy enough for work) and I have been getting more into Rust and other tech that should allow me to get more and more of my daily activities out of the realm of "will only run on top notch hardware because we couldn't be arsed to think about performance."
I'm not GP, but not being able to use a Linux box for work would be a big negative in a future employment decision for me. It's not just a matter of style, but also ergonomics and efficiency (also somewhat in terms of hardware when it comes to Macbook). While I'm open to change that brings improvement, a job forcing me to use tools that I've tried and know will get in my way will make me less inclined to pick it.
Yes. I have been forced to use Windows for communication, and especially the trifecta of Outlook, Teams and Word opened my eyes as to why a lot of my colleagues weren't getting stuff done and were always hung up on weird problems I couldn't understand. Like "why is the reply on this email TOFU and doesn't even answer half the questions asked below": well, because writing proper replies in Outlook is impossible. "Why does this document look like crap even after someone has spent a week editing in all suggested changes?": well, Word doesn't do proper merging of stuff or proper templates. "Why didn't he answer my chat questions from yesterday?": well, because no proper highlights or working history in teams chats...
I feel for all people forced to work like this. I cannot understand employers accepting the massive suck on productivity this causes. For my own sanity, I will charge a premium or avoid such environments altogether.
Btw., if possible a workaround for a lot of the usual driver/VPN/that-one-special-application headaches that force employees to use windows is to get approval for vmware, virtualbox or something, install yourself a linux VM and use that in fullscreen for most things. But of course that is not always possible.
I'm personally thanking god^Wsome good folks at MS for WSL2. Which, from my understanding, is a very well integrated VM, really. But even so, the performance of that thing is just not what it should be.
WSL2 doesn't really cut it. Can't use my own window manager/desktop environment, graphics are kinda slow and sluggish, hardware passthrough is worse than in vmware, etc.
It might be ok for the occasional Linux tool, but I want the other thing: the occasional windows tool, but the rest to be Linux.
Hadn't really crossed my mind that the vmware vm might be more performant than the one baked into windows by MS. That's a bit embarassing, isn't it? :P
Ever since I realized I was fighting a system I have no intention of mastering anymore (my brain cycles are too dear to me for that) I stopped engaging and just accepted it as the nuisance it is.
But "just use vmware" seems like an easy enough fix that I might actually go down that route from now on, thanks!
It would, but I want to stress again that this was not a fault of my employer, nor is it permanent.
It was basically the fault of Dell/Intel to provide proper drivers with my hardware, combined with the worst of timings: the first French started on the day after my hardware arrived, and I had to hastily relocate after picking it up, to avoid being stuck in a tiny temporary housing. This was then the only work-capable hardware in the house. So I couldn't just send it back when I noticed the problems, because it would have meant literally not being able to work for a while. Although with the time I spent trying to make it work on linux, then the nerves/mental health I've spent on using Windows on it, that would have been the better call in hindsight.
Anyhow, given that on-premise work is still not exactly around the corner, I'll build a ryzen workstation as soon as parts become available here, and be done with this. And I'll avoid Dell/Intel from now on.
> On Linux (and generally with FOSS software) whenever I hit a problem, if something didn't work, I could be sure that it was not there because someone didn't want me to be able to do it like that.
You must be dealing with different FOSS software than I usually am. Software quite frequently refuses to let me do things "for security reasons" or because "why would you want to do that". It is very tiring.
This resonates with me a lot.
I started my first "proper" job this year, and the dev env we use is pretty run-off-the-mill: docker, TS, AWS... But there is one big issue and that is that I had to switch to Windows a while back for driver reasons (looking at you, Dell and Intel) and this is the first time in over 9 year that I have used Windows proper. Not a fault of my employer I should add.
In academia, and at home, I have been running Linux for ~14 years by now, so I had skipped Windows 8 and this is my first contact with Windows 10. And while I appreciate how much more stable this system is than my XP from way back when, it feels horrible, and pretty much for the reasons described here.
It's not that Linux was always smooth sailing, or that it was easy, or user friendly in the conventional sense. But there is a huge difference in my relationship to the system:
On Linux (and generally with FOSS software) whenever I hit a problem, if something didn't work, I could be sure that it was not there because someone didn't want me to be able to do it like that. It was always a lack of resources or insight, or both. And people and systems in FOSS are built to enable me to change things.
Working on windows, I tried setting up my PC in the way described in the article. Halfway through I realized that I was just fighting against the system, trying to make it do something it didn't want.
Needless to say, MacOS is not an alternative to Windows for me. They're both dead to me. Lesson learned, gonna vote with my money from now on. I started by ordering an MNT Reform for my personal use (not speedy enough for work) and I have been getting more into Rust and other tech that should allow me to get more and more of my daily activities out of the realm of "will only run on top notch hardware because we couldn't be arsed to think about performance."