• AwkwardLookMonkeyPuppet@lemmy.world
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    3
    ·
    25 days ago

    If documentation is the root cause of that then you should fix that by creating enough documentation to allow your software to continue to work

    Or create a better UI that doesn’t require so much documentation.

    • pivot_root@lemmy.world
      link
      fedilink
      arrow-up
      12
      ·
      edit-2
      25 days ago

      This assumes front-end development.

      From a (dev)ops perspective, if I had a vendor hand me a tarball instead of proper documentation, I’d look very far away from their company. It isn’t a matter of if shit goes wrong, but when. And when that shit goes wrong, having comprehensive documentation about the architecture and configuration is going to be a lot more useful than having to piece it together yourself in the middle of an outage.