• hendrik@palaver.p3x.de
      link
      fedilink
      English
      arrow-up
      21
      ·
      edit-2
      2 months ago

      I mean it also contains great stuff. Niche workarounds, ways to do something more efficiently than some standard library function does.

      You just need a means of telling apart the good and the bad. Because there’s also people smashing their forehead on the keyboard until it happens to be something that compiles. And people repeating urban legends and outdated info. You somehow need background knowledge to tell which is which. AI didn’t invent phrasing some nonesense with full conviction. It is very good at doing exactly that, but we humans also have been doing that since the beginning of time.

    • peopleproblems@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      2 months ago

      Debugging and being able to interpret documentation when it exists.

      But good lord, the amount of programmers I work with that never use an IDE debugger is unreal. I get that you don’t have to, but Jesus Christ, if yout not getting an expected result, it’s way fucking faster to step through the code and see where the data changes then to slap logging into every line and attempt to read the output.

    • wewbull@feddit.uk
      link
      fedilink
      English
      arrow-up
      7
      ·
      2 months ago

      Debugging only teaches logic. Not structure. No amount cut, paste, debug with teach you the factory pattern.