Yeah, I suggest following the age old wisdom of rats on this. Abandon the sinking ship before it sinks with you in it.

Linus has literally talked about that multiple times. He learns just enough to cover what is needed for the video, does the video, then forgets most of.

They are more entertainment and light education. They are trying to target a very wide audience, so they can’t really do deep on things. For actually learning I like LearnLinuxTV and LawrenceSystems.

Chrome Remote Desktop works if she uses the Chrome browser and you only need occasional control when she present to authorize you getting access to her computer.

I think more important than which distro to choose is you setting up remote access for yourself. Tailscale and maybe rust desk or something would be a good idea. Or if you want to go further a vpn connection to a KVM device, some of them support being able to wire into the power button so you have full control. I would also have their account info in your password manager. Then you don’t need them to remember anything because you can do it when needed.

I just googled that model number and “Linux support”. The first result was the Brother website for driver downloads, which does include packages for linux.

This video has a similar discussion about the C++ programming language vs other programming languages that are theoretically better. https://youtu.be/I7fEsbksKRE?is=T53DqwVNM3ps97JY

The summary: An imperfect solution today is nearly always used over the perfect solution that will arrive at some unknown time in the future. Also momentum is a thing.

I agree with having the server run Proxmox like others have said. Check out these YouTube channels for helpful information/guides:

LearnLinuxTV

LawrenceSystems

CraftComputing

Makes sense. Trained on software engineers working that pattern for decades.

My experience has been the more I assume I am an idiot and plan accordingly, the less true it is in practice.

Perl is fine so long as you write code based on the assumption it will be maintained an idiot that doesn’t know the code at all and needs hand holding. And that is why 6 months later I can understand the code I wrote.

My understanding is that Scrum is a tool box. You figure out what tools fit for your team. The problem arises when people are in charge that don’t understand the what the team is doing or the toolset provided by Scrum. They then try to use every tool and it goes poorly.

Funny how tools are useful. But a person who is a tool is not.

Part of me is bothered by those explanations, but if I had to explain GitHub to a tech illiterate grandparent with that much screen space I don’t know if I would do much better.