• @Shayeta@feddit.org
    link
    fedilink
    English
    4
    edit-2
    1 day 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
  • @phantomwise@lemmy.ml
    link
    fedilink
    English
    41 day 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
      21 day 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.

  • @skozzii@lemmy.ca
    link
    fedilink
    41 day 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.

  • /home/pineapplelover
    link
    fedilink
    102 days ago

    Practice I guess. Especially using cli for specific tasks that is done more efficiently on there than the gui.

    Moving files using regex for example is useful. Or finding files with specific phrases in them. Stuff like that

  • @josefo@leminal.space
    link
    fedilink
    92 days ago

    For me it was self hosting, aka not having a choice but to learn. I’ll be dead before using remote desktop for that.

    Also, self hosting gives you real motivation, because you actually need to do things, carry tasks, not just learning for the sake of it. Your efforts get immediately rewarded with functioning things.

    • @utopiah@lemmy.ml
      link
      fedilink
      12 days ago

      real motivation, because you actually need to do things, carry tasks, not just learning for the sake of it. Your efforts get immediately rewarded with functioning things.

      Yes indeed, and that’s true for any challenging skill to hone.

  • @Termight@lemmy.ml
    link
    fedilink
    English
    35
    edit-2
    2 days 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
      32 days 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…

  • @A_norny_mousse@feddit.org
    link
    fedilink
    233 days ago

    Colors. And a nice, readable font. Make your terminal pretty so you feel good every time you interact with it. Think about window dimensions (I personally always find the standard 80x24 too small), maybe set up some manual tiling so you can have two terminal windows fill your screen. Use the keyboard to move around your desktops.

    But mostly, colors.

  • Snot Flickerman
    link
    fedilink
    English
    24
    edit-2
    3 days 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
      163 days 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…”

  • @Matth78@lemm.ee
    link
    fedilink
    233 days ago

    What helps me is to understand what commands acronym means. For instance cp for copy, mkdir for make directory, blkid for block id, ls for list (not too sure about actual meaning for s) and so on!

    Nice tips about ctrl+r to search in command history. Was not aware it existed!

    • Tlaloc_Temporal
      link
      fedilink
      103 days ago

      ‘ls’ is an abbreviation for ‘list’, not an acronym. Like copy -> cp, and the other keystroke saving abbreviations.

    • @josefo@leminal.space
      link
      fedilink
      12 days ago

      works for common flags too, like in df -h, the h stands for human readable, I always find myself mumbling “human” while typing that one