• BB_C@programming.dev
    link
    fedilink
    arrow-up
    58
    arrow-down
    7
    ·
    edit-2
    2 months ago

    Examples ARE usage documentation.

    What value is this blog supposed to be adding exactly?
    The fact that top-level and API descriptive explanations are important?
    The fact that some projects don’t have complete documentation?
    To whom exactly would this be considered new information?

    • anti-idpol action@programming.dev
      link
      fedilink
      arrow-up
      20
      ·
      2 months ago

      This. I can’t count HOW MANY FUCKING TIMES I had to either look up the source code or search GitHub for code using a function from a given library because the documentation was so laconic and/or disjointed.

  • sugar_in_your_tea@sh.itjust.works
    link
    fedilink
    arrow-up
    41
    arrow-down
    1
    ·
    2 months ago

    The only thing worse than a bad example is documentation like this:

    fn do_thing(…)

    Does thing.

    It adds nothing, other than letting you know they were there and decided not to actually provide something useful.

  • Deebster@programming.dev
    link
    fedilink
    arrow-up
    41
    arrow-down
    1
    ·
    2 months ago

    My absolute favourite is when the examples say something like “production code should not be written like this, this is just for clarity” with no indication of what’s wrong with the code.

    Is it just normal Rust stuff like there’s unwraps everywhere and it’s one big file? Does the example have security or performance problems? Is the example unidiomatic or over-verbose or is it ignoring features real-world code would use? EXPLAIN YOURSELF!

    • Nereuxofficial@programming.devOP
      link
      fedilink
      arrow-up
      14
      ·
      2 months ago

      Yeah that’s the fun part!

      Maybe there are also some security implications of the code?

      Because the thing is: That code is probably gonna end up in production somewhere

    • noddy@beehaw.org
      link
      fedilink
      arrow-up
      7
      ·
      2 months ago

      I personally prefer the straight forward everything in one file examples. The worst examples are those that come with its own ad hoc example framework I first need to understand before I can understand the example.

    • crispy_kilt@feddit.de
      link
      fedilink
      arrow-up
      2
      ·
      2 months ago

      It’s probably to encourage people to underdtsnd the example properly then write their own code. Too many people copy/paste examples without understanding them completely.

  • anlumo@feddit.de
    link
    fedilink
    arrow-up
    12
    ·
    2 months ago

    clap and bevy are big offenders there. It’s really hard to learn how to use them due to this.

    • 佐藤カズマ@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      2 months ago

      It sucks that there aren’t (in my limited experience) a ton of engines out there with good documentation (at least that are built in Rust). I’ve started trying to build my own engine, but the complexity and time required are certainly a bit of a barrier, especially for the game I’m working on. (N.B. - The game is nowhere close to being in any sort of state to be shown, so please don’t ask 😆)

      • anlumo@feddit.de
        link
        fedilink
        arrow-up
        2
        ·
        2 months ago

        My experience has been that good documentation is mostly something done if somebody gets paid for the work. People working on stuff in their spare time just don’t care enough to document their project.

        • 佐藤カズマ@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          2 months ago

          That, or they don’t care enough to pick it back up if they ever drop it. Nothing hurts worse than forgetting what you’re trying to do because you don’t even comment your code.