How is logging in to a Windows box with RDP and clicking around different from logging in to a Linux box with SSH and messing around in a trial-and-error fashion with text files though?
Things like „oh this doesn’t work with SELinux enabled, so let’s just disable SELinux“ for example.
I‘ve seen both and I wouldn’t necessarily say I‘ve seen the former more often.
There’s probably as many incompetent Linux admins as there are incompetent Windows admins. At least in my personal experience.
There's no difference in the tasks you you described. I'm not saying it's not possible to do bad work over SSH, I'm saying it's in fact more punishing. If something is 500 keystrokes to do in Linux, you're incentized to do it in an automated fashion to avoid repetitive cli shenanigans. If the same thing is 2 clicks over RDP, who's going to bother scripting that? I'm not opposed to easy, I'm in favor of reproducibility and self documenting scripts.
There's no such incentive with windows because it's so "easy" and things like powershell's double hop and other similar quirks can actually make certian things more difficult to automate.
My point is, at least you can easily translate random CLI poking into scripts. more often than not, an RDP session doesn't lend itself to scripting.
Things like „oh this doesn’t work with SELinux enabled, so let’s just disable SELinux“ for example.
I‘ve seen both and I wouldn’t necessarily say I‘ve seen the former more often.
There’s probably as many incompetent Linux admins as there are incompetent Windows admins. At least in my personal experience.