• NOT_RICK@lemmy.world
    link
    fedilink
    English
    arrow-up
    43
    ·
    4 months ago

    If I had a cookie for every time someone asked me if I could pull together some obscure metric during a 30 minute meeting I’d have the beetus

    • jballs@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      23
      ·
      4 months ago

      Same. Especially since I’ve been building EDWs for most of my career. People are always surprised that it actually takes time to integrate with different systems.

      “What do you mean you can’t just pull all the data out of this system that we don’t have database access to and are still building out the APIs?”

      I kid… The people asking for stuff don’t know what backend databases and APIs are.

        • jballs@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 months ago

          Maybe this makes me old, but I much prefer a written document explaining how an API works over Swagger.

          • jcg@halubilo.social
            link
            fedilink
            arrow-up
            2
            ·
            4 months ago

            I prefer a hybrid approach. A document explaining some common things to do and generally the idea behind why the API is structured that way (shows me you actually thought about it, and makes it more logical to find different parts of it without necessarily looking it up), and then an API spec showing all the parameters.