I’ve been doing the OverTheWire Bandit over the past couple of days and have become stuck on the earlier levels. I deem this very embarrassing as this is supposed to be an “easy” and “recommended for beginners” type of puzzle that requires hands on understanding of the Linux terminal. But I have been using Linux for 9 months now, I wouldn’t do the most complicated things (other than break my whole os) only the things required to make my overall user experience somewhat enjoyable. Now this makes me very sad to come to the conclusions that I may be below the average Linux beginner which I didn’t know was possible according to my knowledge. I am only asking of tips and tricks to these puzzles and maybe to positive reinforcement to make feel better about myself. Now I will not tolerate spoilers as in the official rules of OverTheWire clearly states, and I hope you will follow this rule for the better sake of my learning and understanding of the Linux terminal ( and for the sake of the game itself)

  • hyperencabulator@lemmy.today
    link
    fedilink
    arrow-up
    2
    ·
    7 hours ago

    Man I loved OTW! I need to get back into it.

    I rarely used Google bc I apparently have a masochistic desire to make things harder than they need to be, I mostly just looked at all the man pages (type man command name here) and it usually brings up a helpful manual that has it’s own controls to navigate with. Helpful to know that ‘Q’ is the key you want to press to leave the man page and go back to the terminal. It took me a few tries to learn that. But seriously, I had fun just getting lost in all the features and options in each page for awhile even if it wasn’t the fastest way to complete the levels. Man pages are mostly dry and sometimes funny but they will get you through a lot of Bandit without using google IMO.

  • kepix@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    13 hours ago

    “man i have my little app, but i dont distribute on any of the stores, dont provide install files or compiling tutorial. i have no idea why noone uses my awsome application.”

  • Thorned_Rose@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    3
    ·
    1 day ago

    Are people just not exploring websites anymore? Surely my household can’t be the only one where if you don’t know how to use a website or find something on it, we actively explore it. (Dodgy sites notwithstanding, I mean safe and legit sites). Am I strange that if I can’t work out how to use something, I look for a manual. And barring that, I try different things, trouble shoot using logic, etc. to work it out for myself… I’m not a programmer but I can’t say as I had a great deal of difficulty working out how to use Github (as a consumer) for myself…

    • 404found@lemmy.zip
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      1 day ago

      I’m good at figuring things out. I don’t know how to get code on GitHub even though I’ve lazily tried multiple times.

      I get frustrated because I’m looking for something that I feel should be easily found (code on GitHub). Instead I’m given a puzzle I have to navigate through. I thought getting the code off GitHub was going to be the easiest part of my project. Nope.

      Everyone wants your data so apps and websites are intentionally designed to keep people moving through them. I’m not saying that is what GitHub is doing here but it’s the reason I have little curiosity to explore apps and websites anymore. It’s flawed by design. Not because the opportunity to improve the end user experience hasn’t occurred yet.

      • recarsion@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        1
        ·
        17 hours ago

        You haven’t said if you want to work on the code or only want to run the software, but if it’s the latter you don’t actually need the code usually. There’s usually a Releases page (I believe it can be found on the right side bar) that will have the software built and packaged for different systems. So unless it’s not available for your OS and you need to build it yourself (which can be a bit of a pain to figure out) you don’t need the code.

      • Hugh@programming.dev
        link
        fedilink
        arrow-up
        5
        ·
        24 hours ago

        Install git. Then type git clone <url>

        For example to download miniaudio you would type

        git clone https://github.com/mackron/miniaudio.git

        And it downloads all the code for you. There’s a button on github that says “code” if you click it you can copy the URL for cloning.

  • CarrotsHaveEars@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    1 day ago

    I’m surprised though, to find out it’s only PR #1349. With the repository public for all these years, I expect more idiots than 1349. 😏

  • IEatDaFeesh@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    2 days ago

    He’s got a point. As someone who’s familiar and uses GitHub all the time, there are moments of frustration where it’s like… “just let me be braindead and have it work”

    • monovergent@lemmy.ml
      link
      fedilink
      arrow-up
      9
      ·
      1 day ago

      Especially github projects with instructions like:

      On Debian/Ubuntu, install from my PPA

      sudo add-apt-repository ppa:totally/well-maintained
      

      or on Hannah Montana Linux, build with

      python2 mk-dependencies.py
      fartify-next build --forceit 
      
    • Joelk111@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      1 day ago

      I forget how to find releases or download the code (instead of forking the project) just about every time I use github. He’s got a point but god damn he also seems insufferable.

  • Fecundpossum@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    2
    ·
    2 days ago

    The big secret no one tells you about about bandit, is you have to read the fucking manual. No really. RTFM. Each level tells you what commands you may need. The manual pages for those commands tell you the context and syntax of their usage.

    That is literally the only tip/trick. Read the instructions.