• Shayeta@feddit.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    3 months ago

    Knowing:

    • pwd, ls, cd, cat/less, cp, mv, rm, rmdir, rm -rf, ls -lah
    • command --help
    • man command | grep thing I care about
    • bonus points if you have tldr command installed
  • Nis@feddit.dk
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    Clear instructions on how to do a clearly defined, specific task, in a failsoft manner, faster and easier, which helps them in a project they are doing now.

  • railcar@midwest.social
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    Using computers since before GUI was available… Sometimes I think we ought to go back to it

  • phantomwise@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    I have no clue… I grew up on Windows 3.11 and I thought Windows was kinda lame while MS-DOS was the coolest thing ever because you typed things like magic spells 😅

    • bitjunkie@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      This right here (more or less - first home PC was Win95, but it still relied pretty heavily on DOS, esp for games). I loved the RPGs where you typed in your actions, too.

  • cmnybo@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    Play around in a virtual machine so you don’t have to worry about messing anything up. Start with the basics such as navigating through directories and creating, editing, and moving files. If you break something, just restore a snapshot.

    • a14o@feddit.org
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      The way I usually start teaching using the console to my (very much non-tech) students is set up a safe container and then let them type whatever, invariably generating a lot of error messages. Then I challenge them to generate different error messages, “gotta catch em all” style. Then we talk about the error messages and what they might mean. After this exercise they usually get the basic idea of command – response, what to look out for and how to compose valid commands.

    • prole@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      Or just use Time Shift or a similar tool. I broke my first linux install like a dozen times, and I learned so much about how my computer operates in the process.

  • skozzii@lemmy.ca
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    When you aren’t in a rush try to do stuff in command instead, looking for a file? , try to find it in command. Need to copy and move a folder? Don’t use your file manager, use the command line instead.

    Eventually you will piece together the bits you learn and it starts to make sense, and then you feel like a God. Lol.

    • pineapple@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 months ago

      I 100% agree. I’m still relatively new but this helped me become much more confident.

  • Snot Flickerman@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    3 months ago

    In my experience repetition helped. Not memorization, but more like muscle memory.

    Also, ensuring to never copy and paste commands but to type them in manually yourself. It’s hard to enforce this on yourself, but worth it.

    I appreciate that this article started with “ways to reduce risk” because that’s an extremely valid concern and tied to why you shouldn’t ever copy and paste. The one time in my early Linux forays where I copied and pasted I wiped the wrong drive, it definitely taught me to always manually type it in and not get too lazy, because what you copied might not match what you want to do exactly.

    • remotedev@lemmy.ca
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      Also, ensuring to never copy and paste commands but to type them in manually yourself. It’s hard to enforce this on yourself, but worth it.

      “Command: sido not found…”

  • 33manat33@feddit.org
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    Okay, this is not Linux-specific, but it’s about a transferable skill:

    What helped me get comfortable and learn a lot of basics was setting up NetBSD. The basic install throws you into a basic command line, with no graphical interface installed and not even the internet configured. But the online guide for setting the system up is incredibly well-written and teaches you all the concepts you need to know.

    After doing this, I was familiar with a larger set of terminal commands, knew how to use vi, had a bunch of practice setting up config files in CLI and even finally learned how pipes work. It’s a very enjoyable experience, the guide is so good I didn’t feel overwhelmed once and anything you have to look up is tied to a problem you’re solving (like cursor movement in vi).

    It also teaches you how NetBSD is structured. It’s not Linux, but similar enough to understand a lot of how and why things are done in Linux systems

  • lordnikon@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    3 months ago

    To things that helps no mater your skill level the tab key is your best friend and man pages are great but if those are overwhelming install the package tldr then you can use the command tldr and the command you are trying to run to give you helpful examples of how to use that command.

    Also old users don’t remember long commands if we use a command more than once. You save it to your bash alias file to create your own commands.

  • applemao@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    I think just doing it more, and thinking it’s cool to interact more directly. At least that helps me. I do feel bad for dyslexic peiple though, it’s a lot harder for them to use CLI.

    • Random Dent@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 months ago

      Yeah that was it for me. Just keep regular backups and bear in mind that you’ll probably break stuff at first. But once you get the hang of it, it’s like a whole other level of control over your system.

      Also I’m not dyslexic but would things like tab completion and aliases help maybe? I sometimes shorten often-used commands with aliases just for convenience (as an example, I use rsync a lot, particularly the command rsync --ignore-existing -ravwhich I just shorten to rs to save time) so maybe that could also be used to avoid mis-spelling?

      • applemao@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        Thats a good idea, i have not made any aliases yet. Also remembering all of those aliases is another challenge ha. I keep a text file named commands on my desktop with a whole bunch of commands I forget.

        • Random Dent@lemmy.ml
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 months ago

          I have some mapped to super simple aliases too like e1 to reboot, e2 to shutdown etc. I don’t remember why I started doing that, but that way I only have to remember which number does what lol.

  • ABetterTomorrow@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    I’m trying to make it a regular thing but my problem is I like to get my hands dirty by working on projects. The snag is that I get stuck a lot due to not knowing basics. My personality gets in the way = get dirty and learn fast(not necessarily shortcuts). Maybe I haven’t found that right source to learn that not too beginner and not too intermediate. Maybe a cool cluster of small projects to setup your computer then environment to setting up projects to do your everyday life takes to what you really want to learn.

  • southsamurai@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    Really specific here, but font control.

    Us folks with dyslexia in its various expressions have trouble with command line. If you can’t read a specific command, good luck ever getting comfortable with it. You can’t error check yourself, so until you build up memory, you’re kinda screwed if you can’t use the fonts that are available.

  • Termight@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    3 months ago

    Mastering the command line? A few observations. First, consult and take notes (yes, even seasoned terminal veterans forget syntax.) Secondly, embrace tab completion. It’s your friend, and a surprisingly effective substitute for remembering every single command. Third, the true test: procure a VPS or remote server and exclusively use the command line. No GUI crutches allowed. It’s a digital wilderness, and you’ll learn to navigate it.

    Lastly, and this is non-negotiable: keep a terminal window permanently resident on your desktop. Consider it a vital organ, deserving of its space. It’s a constant reminder of the power you wield, and a readily available portal to a world beyond the pretty buttons.

    • N0x0n@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      Hehe, I’m doing this all the time now ! 3 years ago when I started my linux/self-hosted server journey with debian: CLI only !

      Was difficult at times and had a few breakdowns (most got fixed the next day… Sleep/taking some time off really helps !!!)

      One thing I’m still bad at… Is taking notes. Haven’t found a good way take IT notes. And I tried sooo many different approaches…

    • WalnutLum@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      On that front: to developers-

      Please make sure you include bash completions for your tools