I just can't bring myself to go to the effort of documenting a thought and adding links/tags unless it is something I predict that I will need sometime in the future and won't just remember. Due to this, my Obsidian vault is pretty much a collection of a bunch of temporary to-do lists and then some folders with specific reference information. If I'm linking thoughts together I'm doing it real time in my head, anything else takes me too far out of my thought process.

I can see it if you are a person working in academia or a writer where you may be generating concepts that you want to link together in the future. But as someone that does project type work, I'm following too much of a defined process to see any benefit.

I've got suppliers who I can send a difficult part to and know that I'm going to get exactly what I expect, faster and cheaper than just about anyone else. It took a few years to get to that point, but these few vendors make it really hard to go with anyone else, much to the chagrin of the sourcing team who rightly recognize it a risk to rely on just a few suppliers.

Once you get to a certain type of supplier you end up running into the problem where their processes are such that they won't do anything without you clearly documenting it. They simply refuse to make any assumptions on your behalf. They can be so frustrating when you are used to the other way of doing it. I simply cannot answer some questions because I'm so used to my other suppliers just doing it correctly and haven't ever asked about it.

This is an overblown issue. For the most it is a case of installing the proprietary driver package following the instructions for your distro. One more step than AMD which just works, but not really any more difficult than installing another package.

My big tip if you can't find a button there is always the search bar. Just search the command you are looking for, it will even show you where the button is located for next time. That said, they don't move things around that much from year to year, I'm surprised if you can't find a command in a tutorial made in the last 10 years.

The features you are talking about sound like you want to be doing surfacing, which is definitely a more advanced modeling technique that I only recommend trying to learn once you understand the basics and can predict how the software wants you to model something.

One of the big barriers to having more people use Linux is having the software packages they use to actually do work available on the platform. Image editing is the most popular software type that isn't really available on Linux with an equivalent to the commercial package that everyone uses.

This has strong energy of "Teach your kids how to play Magic, they won't have money for drugs."