18 month project is winding down. I suspect it will have 1 use in the next 4 years we are supporting it.

The tool is basically a copy of the S3 browser, only shittier. The license for the S3 browser is only 20 bucks btw.

  • d6GeZtyi@lemmy.world
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    edit-2
    1 year ago

    It wasn't the most fun part of the project, and it was targeted at non-moving home devices so a more powerful wifi logic wasn't really needed. In the rare scenario where the customer didn't see its wifi network, he/she could just refresh the list.

    I basically just added an ugly timer and moved on more important things.

    • embix@feddit.de
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago

      non-moving home devices

      There still is a use case - not that common in America but very common in (not only Europe's) metropolitan areas:

      If the devices are located in a dense urban residential area (say Berlin Gropiusstadt in the 11th of 20 floors) you have a lot of neighbors with wifi, and - at least on 2.5GHz - roughly a third of their wifis will use the same or overlapping frequency range. In the evening, when everyone and her dog streams the newest Season of Bridgerton those will send relatively short bursts for buffering the next five-ish(?) minutes.

      This of course interferes with your measurement if you happen to measure at exactly the same time, so having multiple samples instead and providing an aggregated value is - for this scenario - more helpful.

      OTOH: it all depends on the use case of those appliances - if you don't have competitive gamers who wonder why they sometimes lag in your valued customer list, that's a non issue (and if they actual were competitive gamers, they should use an ethernet/fiber cable instead of wifi, obviously).

      And you probably did not get that much time allocated to add the delay, so going with another variant could get you in trouble if it's taking too long.

      • d6GeZtyi@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        Thanks for the information on those situations, I didn't know.

        It was actually mostly targeted to (multiple) European countries. Yet I would probably just re-do it the same way if I re-did that, I prefer the simplicity (of the code) of having the user manually refresh the list for such niche issues over a complex code others would have to maintain. Moreover, the wifi just has to be configured once, at first install.

        And you probably did not get that much time allocated to add the delay, so going with another variant could get you in trouble if it’s taking too long.

        When I read that, I'm happy to not rely on tickets system / scrum or to ever get into trouble because I'm doing the right things. I would probably quit a job like that, it sounds like hell to be considered that way.