• IDatedSuccubi@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    This is what I and many other programmers have done (not the removal, but fake delays), because it improves user experience, actually:

    1.When the user clicks a button that should take long in their mind (like uncompressing a zip file etc) but is actually fast, it might seem like something is wrong and it didn’t work

    2.When the user transitions between layouts of the application, if it loads everything too fast it will look too abrupt, a fake delay will be made here if a transition animation is not possible/doesn’t fit

      • IDatedSuccubi@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        I’m pretty sure it’s either a myth (that it doesn’t work) or some US-centric thing, because when I worked as a delivery guy, I used to go through probably hundreds of different elevators in high-density residential buildings, and most of them have doors that stay open very long to allow baby strollers and heavy appliances to be placed inside, and on pretty much all of these the door closing button works, immediately closing the door

    • alokir@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      I was working on an enterprise web application, there was a legacy system that everyone hated and we replaced it with a more modern one.

      We got a ticket from our PO to introduce a 30 sec delay to one of our buttons. It sounded insane, but he explained that L1 support got too many calls and emails where users thought said button was broken.

      It wasn’t, they were just used to having to wait up to 5 minutes for it to finish doing its thing, so they didn’t notice when it did it instantly.

      We gradually removed that delay, 10 seconds each month, and our users were very happy.

  • Ducks@ducks.dev
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Used to work with a guy who would put 3 second sleeps after every line in our Jenkins file. He would then say how he’s so busy because he has no time when he’s always waiting for builds to run.

    Chris, everyone knows what you were doing.

  • fibojoly@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    1 year ago

    Who needs to add Sleep calls when you can just do your shitty every day naive implementation and let your future colleagues fix your mess.