• lagoon8622@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    6
    ·
    4 days ago

    This diagram is classic “engineer developing a solution for a problem that doesn’t exist in a domain they don’t understand”

    • Feathercrown@lemmy.world
      link
      fedilink
      English
      arrow-up
      25
      arrow-down
      1
      ·
      4 days ago

      The diagram does have benefits. For example it shows which steps can be performed in parallel if multiple people are cooking.

      • 0ops@piefed.zip
        link
        fedilink
        English
        arrow-up
        9
        ·
        4 days ago

        And concise! No more frantic scrolling on my phone with batter-covered fingers

        • Feathercrown@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          ·
          4 days ago

          Similarly, it also easily identifies which part of the recipe each ingredient goes to. You can do this by splitting up the ingredients list as well, but that doesn’t really go against it being a good idea.

          • lagoon8622@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 days ago

            I’m a software “engineer” and also passionate about cooking. Both are arts. You can’t reduce it to an algorithm

            • Feathercrown@lemmy.world
              link
              fedilink
              English
              arrow-up
              1
              ·
              2 days ago

              Same; but imo while “real cooking” is an art, following instructions (a recipe) is basically an algorithm. At least, expressing it as one doesn’t change the opportunities for artistic expression.