I’ve been wanting to learn how to code for a while so I figure now is as good a time as any to start. I downloaded VS code on my laptop for python but I don’t really know end product I should try to code and I also am just bad and barely know what I’m doing. Does anyone here have any advice on what to code and how best to learn?

  • blankmind@lemmy.world
    link
    fedilink
    arrow-up
    19
    ·
    1 year ago
    • Hello World
    • Read a file
    • Write a file
    • Read a file and loop through it line by line, printing each one (for loop or equivalent)
    • Program that consists of 2 or more source files

    What I’m getting at is instead of a full program, write code snippets and small programs. In doing this eventually an idea for something larger will pop into your head.

    • James@lemmy.ca
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      1 year ago

      In addition to what this guy said, don’t just use libraries to skip steps when writing small programs.

      For example when parsing a file you will often use the split and strip functions in python, but learning how to implement these by yourself will teach you more.

      To really learn fundamentals you should try and implement most operations yourself. It’s why in my opinion C is a better language to start with, because it forces you to learn the fundamentals.

      • Max-P@lemmy.max-p.me
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        1 year ago

        I’d say it depends on the learning style. For some people, it’s a lot less demotivating to start as just plumbing libraries together to get the end result than starting from the deep end. Same debate as starting with ASM vs starting with Python.

        • James@lemmy.ca
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          I see your point, but I would almost argue that starting out with all these shortcuts available in high level languages is ‘jumping into the deep end’ itself.

          When a newbie sees obscure error messages in some of these libraries they might not have any idea what they mean or why they were triggered. My opinion is that having a smaller set of tools to start is actually simpler despite being able to do less with them.

          I’m slightly biased because I started with C 😅

          • Max-P@lemmy.max-p.me
            link
            fedilink
            arrow-up
            4
            arrow-down
            1
            ·
            1 year ago

            Started with C++, definitely wasn’t easy. I ended up giving up and revisiting a couple years later and PHP/HTML was a fair bit less to take. I did end up revisiting C++ and making an archive format for my game engine. These days I definitely start by the low level, even libraries I jump to the low level features/long form before going to the nicer abstractions for the sake of understanding what’s going on under the hood. It’s definitely valuable too.

            Just pointing out different styles of learning exists, OP can choose whatever fits better for them. I’ve known people that good completely demoralized because it was a bit much to take to think about how big an integer is in memory and arrays and whatnot. Especially if you approach it with making games, focusing on player moment and map scrolling can be more intuitive to learn the basics and slowly migrate to lower level things. I have friends that started with 6502 or Z80 assembly (good ol’ Ti 83+ calculators) and they liked that way better because it made them appreciate what compilers really do better. Really dependent on the person.

            I advocate for whatever works better for the learner, whatever makes them not give up and whatever keeps them going.

            • abhibeckert@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              edit-2
              1 year ago

              Started with C++, definitely wasn’t easy. I ended up giving up

              I made it about as far as std::cout << "Hello World!"; and couldn’t figure out wtf cout was or progress from there.

              Eventually, nearly a year later, I started over with a simpler language (Basic) and maybe five after that I realised my IDE just wasn’t setup right - so cout literally did nothing at all.

    • groucho@lemmy.sdf.org
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Yep! And then read argv for command-line parameters + a parser. File IO + command-line controls gets you a shell of a utility to work with. Then grab a package you like the look, bring it into your project, and do something with it (image manipulation, network stuff, whatever…)

    • slazer2au@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      This is a good start.

      My latest python script loads my monthly banking CSV, arranges the columns in the correct order, assigns categories based on the merchant, and finally exports the data to a new CSV.