• lime!@feddit.nu
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 day ago

    your writing overall is good! it’s just a matter of information priority.

    here’s a tip, dunno how applicable it is but i use it when writing technical documentation:

    for each step, explain to yourself why you’re doing it the way you are. if it turns out you caused the step to be needed, rather than it being required, you probably need to rethink, or at least add the explanation to the text.

      • lime!@feddit.nu
        link
        fedilink
        English
        arrow-up
        1
        ·
        17 hours ago

        this is more focused for sure, but it lacks the enthusiasm of the original. if i was trying to do this for work, i would appreciate how quickly it gets to the point. however, it no longer reads like this is something you’re interested in. it reads a bit wooden. i get that would happen after you’ve been told to correct your style though.

        to be clear, the original article doesn’t need to be rewritten. for the future though, when you want to tell the story of how you got something working, include your reasons for doing something a certain way. if you need a self-inflicted complication, that’s not really a part of it (unless it’s funny)

        • eric@lemmy.caOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 hours ago

          I’m picking up what you’re throwing down. I’m writing one on qBittorrent and will take that into considering. Thanks for helping me.

    • eric@lemmy.caOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 day ago

      That’s a good tip. Thanks. I think I might tweak the existing posts for readability.