Are you trying to say I’m not a newbie with over 20 years of experience?
Comment on I'm guilty of not reading the f..ing documentation
yesman@lemmy.world 2 weeks ago
It’s weird that Linux certification requires rote-memorization of commands. The only people who make any effort to memorize commands are newbies and people studding for exams. You will always have access to bash history, man, and --help, even from an offline machine.
Every command I’ve memorized is simply the natural process of repetition. Is that your experience?
RamblingPanda@lemmynsfw.com 2 weeks ago
mvirts@lemmy.world 2 weeks ago
People are worried about losing skills to AI while all the skills have already been lost to Google and stack exchange 😅
LucidNightmare@lemm.ee 2 weeks ago
Mine too. Been tinkering with Linux since I was a lad, sudo apt get / sudo apt update is ingrained into my brain.
Now, after running openSUSE Tumbleweed, sudo zypper ref / sudo zypper dup
Still a Linux noob, but I have never loved an operating system more than I have openSUSE. :)
med@sh.itjust.works 2 weeks ago
Yes. But also, despite having done it literally thousands of times, I still can’t tell you which way round to put the target and the link name for a softlink on the first go.
My first guess is always
ln -s $NAME $TARGETNo amount of repetition will fix this.
shrugs@lemmy.world 2 weeks ago
My trick to remember:
You can link to a target without giving a name to the link. ln will use the basename of the target file then. You can’t create a link without a target, so target has to go first since it’s not optional. Did it for me
turkalino@lemmy.yachts 2 weeks ago
I used to have that problem with ln until I realized it’s essentially the same ordering as cp: source, then destination. The source being the existing file that you’re linking to, and the destination being the link that you’re creating
qqq@lemmy.world 2 weeks ago
I feel seen
mvirts@lemmy.world 2 weeks ago
🤣 same