• ReallyKinda@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    Idk as long as you can communicate exclusively in flow charts you can communicate with software engineers pretty efficiently

    • bleistift2@feddit.de
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 months ago

      Let me share my point of view as a programmer: The average person has no clue how detailed a computer program needs to be. You may think, “this process has only three steps, yadda, flubber and diddly”, but when you sit down and try to program this, you start asking questions like “if the user removes the program during the yadda process, should we add zero flubberees into the diddlydoo and send it off or should we not send the diddlydoo, and should the user be notified? Or should we maybe try to reinstall the program and start again from the yadda? Does it make sense to keep the inputs from the flubber, or is this likely a new process that’s independent from the first attempt? Is it sensible to enter a non-integer number of flubberees? A negative number? No number at all? Do we need to tell other users that a user is concurrently doing this process?