First thing I’d do is to look at the client (fedora) journal for anything funky happening.

‘sudo systemctl status nfs-client’

Since it’s random I assume you won’t have any timeout in your /etc/fstab but it might be worth taking a look anyway.

Be aware that if the network drops the NFS will be disconnected and won’t auto-reconnect so this could also be the issue.

I don’t know if it plays well with container mounted volume, but looking at autofs could be a solution to auto-remount the share. I use it profusely for network mounted home directories.

“OK then do me a favor, shut it down, unplug the power for 5 second and plug it back in”

I’m currently trying Fedora Kinoite and from the get go the hassle of getting a proper Firefox+codecs to watch online videos feels like a major step back.

Then you have the issue of installing software in flatpack (is: vscode, texmaker) that are either not fully working of need to have their access tweaked. Atomic distros appeal is to “just work” it doesn’t seem like it does.

alias fuckit=“git add . && git commit -a && git push -f”

Siemens makes NX. Catia is made by Dassaults. They compete for the same space in the market

It’s a software that is used extensively in aerospace and car industries. It’s also ludicrous how expensive the licenses are.

It’s hard to beat for completeness of functions but also for complexity.

Working with Catia is the other way around, no amount of documentation is complex enough that you really understand what something does or can do.

I disagree but you do you.

Edit: dammit you edit your comment a lot for someone who claims to know how to write code properly.

Because everyone knows a function stops at the if-else. Nothing ever happens afterward.

I say ess cue ell for the sake of uniformity because it’s not Mysequel nor Postgresequel and the language changed from Sequel to the acronym SQL in the 70s so not really in the “too new” ballpark anymore.

There’s nothing limiting what a comment should be as far as I know.

As an example of what I mean, I’ve seen in a 10k+ lines python code a few lines of bit manipulation. There was a comment explaining what those lines did and why. They didn’t expect everyone to be proficient in bit manipulation but it made it so that anyone could understand anyway.

IMHO the issue in this situation is not the comment but that the person updating the code didn’t do his job properly which shouldn’t be an excuse not to do it from the start.

I don’t care how much you think your code is readable, plain text comments are readable by everyone no matter the proficiency in the programming language used. That alone can make a huge difference when you’re just trying to understand how someone handled a situation.

New employees are responsible of at least 75℅ of documentation clarification and process overhaul.

Keep everyone awake and on their toes.

I’m always scared when adding automation around manual inputs that people won’t follow the proper syntax and screw everything.

My previous job was to write official documents for engineering changes in an aerospace company, standardized English and everything. Even with the really strict guideline we had typos, self-inculpating wordage and the likes quite often.

My guess is that commercial customers will get first choice leaving almost no stock for scalper/end-users.