• zalgotext
      link
      fedilink
      arrow-up
      20
      ·
      10 months ago

      The important part is that you know how the code you copy works.

      • spiderman@ani.social
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        2
        ·
        10 months ago

        i wish my deadlines are not hard enough so that i could actually take time to learn everything from the code i copy.

        • corsicanguppy@lemmy.ca
          link
          fedilink
          arrow-up
          4
          arrow-down
          1
          ·
          10 months ago

          Don’t worry – you don’t have to cope with too-short deadlines after you’re dead. Up to that minute, and especially after graduation, though, it’s all deadlines and priorities. Grok the concept.

          You’ll find the head-fake (as Randy Pausch calls it) is teaching you to manage your time and priorities WHILE you’re learning your craft. Like how we learned C++ in an algo course by having the Prof teach Zero C++ and expecting us to pick it up.

          • Arcka@midwest.social
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            1
            ·
            10 months ago

            Sure, committing to a deadline is reasonable if you are included in the decision calculus of scope vs time. Part of that should be to include space for learning as needed to understand anything you’d copy.

            Omitting that is a recipe for low quality garbage and not only will the code suffer, but the organization also will while all the staff fall behind any competitors who make the investment.

    • uis@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      10 months ago

      How did they not die as babies, considering that they were likely too stupid to find a tit to suck on?