Fair enough. LLMs and even Google have nuanced drawbacks, I personally try to give the creator of software some say into its usage simply because the intended usage is better tested than any changes I may need in the future.

At the and of the day learning is key.

Don’t worry, its made for you to pick it up as you go. Make sure you familiarize yourself with the 3-2-1 backup principles first. The idea that your data survives regardless of anything that may happen is important. You (and I trust me) will bork things and accidentally erase precious data. Be prepared to recover from that. Simple solutions you understand and test > complex info secondhand.

You ddint ask but I will mention you shouldn’t encrypt anything yet that you dont have to. Also use as little software as possible I.e. stay away from github repos.

I haven’t had that experience. More often than not I’ve found properly made software breaks in ways that tell you why. I seem to get stuck going in a circle of doom with llms.

I believe putting in the effort to understand the man format is a great start. Man was made to be helpful and nearly universal.

I second the idea of breaking down the commands mentally and understanding how CLI really works. You don’t need to go super deep but some stuff like $PATH and general bash or zsh will 100% make everything a breeze. These are tools like swinging a hammer you have to learn the motion.

You’re not wrong, If it best suits needs AGLPv3 is swallowable.

GPL3

I would suggest avoiding anything that is a “community” or “personal use only”. If its not fully open its not worth it.