As a one time noob I may have done this once or more.
To get one thing working I borked everything.
Understanding permissions is pretty basic. But understanding permission requirements for system and user apps and their config and dirs can be a bit overwhelming at first.
Thinking a little change to make your life simpler will break something else doesn't always register immediately.
Shit, even recently, wondering why my SSH keys were being refused and realising that somehow i set my private keys world readable.
Possibly but my role was such Im really only supposed to be working on my project and not monkey with the server which is used by other projects. I don't think it was a restriction I think it was just laziness by whoever set it up.
Sometimes your package manager asks you for root password every minute while doing few hours long update and cancelling process if you don't enter anything for few minutes, "yay" aur manager looking at you, and you got to do other things than sit and look in the monitor all day long, things like cleaning house or touching grass for example
Our crappy vendor software will only function if IPv6 is disabled network wide. Even if one machine has it enabled, the whole thing breaks
Lol our former crappy vendor solution required to be run directly from AD Administrator. Pure luck the entire business didn't collapse before we replaced it.
Ubuntu uses Snaps for a lot of the software, thus, when you write sudo apt install firefox that is actually an alias for "install firefox from snap". Snaps get installed locally, not on the system (globally, for all users), but as a user, so you really can't do much damage when you actually didn't do anything to the system in the first place.
Do sudo shit on any other distro that doesn't have a company behind it, see what happens.