I’m really enthusiastic about anything involved with Unix/Unix-like operating systems and their ecosystems (Mostly Linux and a bit of BSD variations). I also know a couple of programming languages including C, C++23 and OCaml. But other than doing a couple of tiny projects mainly to practice my programming skills in the languages mentioned above, most of my experience is theoretical and it comes from reading books, blogs and watching conferences.

I’m interested in gaining “actual” experience by doing systems programming related projects but I’m not sure how to get started. How do I decide on which topic to choose? A topic which would not be too overwhelming and actually achievable? And how do I gain the background knowledge needed to implement a project without ending up copying and pasting everything from existing implementations?

Thank you!

  • fuzzzerd
    111·
    8 months ago

    The reality is that you can’t. So accept that going in and realize your learning will be iterative.

    You’ll be overwhelmed, that’s OK. Copy paste code until you get something working. Here’s the key. At that point stop, go back and understand the code you copied, why it works, and then try to rewrite it differently now that you know what worked.

    Metaphor for writing. Start with a quote, then paraphrase it. Do that enough and you’ll start to be able to adlib and come up with your own solutions.

    • Ephera@lemmy.ml
      5·
      8 months ago

      Personally, rather than copy-pasting code, I like to actually copy it by typing it out, especially if I’m still learning the syntax of a new language. It just makes you read the code much more attentively than glancing over it after it’s already written.

      • fuzzzerd
        3·
        8 months ago

        Absolutely. That’s a fantastic way to do the “copy/paste” I definitely think it helps when learning new language.

    • aidanOPEnglish
      2·
      8 months ago

      That’s a very good point. Thank you!

    • Hammerheart
      2·
      8 months ago

      I learned something very valuable relatively early in learning how to program: sometimes, if you do things you don’t understand enough, the understanding will come as a byproduct of just doing the thing.

      I had been stuck in a “i must understand the fundamental nature of everything i do before i do it” mindset, so this was quite revelatory to me.