• sunniegoldie@sh.itjust.works
    1·
    5 months ago

    One of the worst IT setups I’ve encountered involved a company using a patchwork of outdated systems and manual processes. They had multiple disconnected applications for different functions—some were on-premises and others were in the cloud, with no integration between them. This led to data silos, inconsistent information, and a lot of manual data entry.

    After researching for months, finally the company adopted an ERP system which has greatly improved their situation. This system eliminated the need for manual entry, reduced errors, and provided a centralized view of their operations, leading to better decision-making and efficiency.

  • mozz@mbin.grits.dev
    1·
    6 months ago

    Startup in a rented house in a residential neighborhood

    “Router” was an old PC running Linux with a few network cards, with no case, with a household fan pointed at it to keep it cool

    Loose ethernet cables and little hubs everywhere

    Every PC was its own thing and some people were turbo nerds. I had my Linux machine with its vertical monitor; there were many Windows machines, a couple Macs, servers and 2 scrounged Sun workstations also running Linux

    No DHCP, pick your own IP and tell the IT guy, which was me, and we’ll set you up. I had a little list in my notebook.

    It was great days my friends

    We went out of business; no one was shocked

      • mozz@mbin.grits.dev
        1·
        6 months ago

        It was the best of times, it was the worst of times. I turned in a time card once that had over 24 hours of work on it in a row. The boss was dating a stripper, and she would sometimes bring stripper friends to our parties and hangouts. We had ninja weapons in the office. The heat was shitty, so in the winter we had to use space heaters, but that would overload the house’s power which would cause a breaker to blow which obviously caused significant issues, so a lot of people would wear coats at their desks in the winter, but that obviously doesn’t do much for your typing fingers which was an issue. I frequently would sleep in the office on the couch (a couple of people were living in bedrooms in the upstairs of the house).

        Like I say, it’s not surprising that we went out of business. It was definitely pretty fuckin memorable though. Those are just some of the stories or right-away memorable pieces off the top of my head.

  • Blizzard@lemmy.zipEnglish
    1·
    6 months ago

    My current company has a script that runs and deletes files that haven’t been modified for two years. It doesn’t take into account any other factors, just modification date. It doesn’t aks for confirmation and doesn’t even inform the end user about.

      • Blizzard@lemmy.zipEnglish
        1·
        6 months ago

        Thought about it but I use modification date for sorting to have the stuff I’ve recently worked on on top. I instead keep the files where the script isn’t looking. The downside is they are not backed up so I might potentially lose them but if I don’t do that, then I’ll lose them for sure…

    • eclipse@lemmy.world
      1·
      6 months ago

      I actually disagree. I only know a little of Crowdstrike internals but they’re a company that is trying to do the whole DevOps/agile bullshit the right way. Unfortunately they’ve undermined the practice for the rest of us working for dinosaurs trying to catch up.

      Crowdstrike’s problem wasn’t a quality escape; that’ll always happen eventually. Their problem was with their rollout processes.

      There shouldn’t have been a circumstance where the same code got delivered worldwide in the course of a day. If you were sane you’d canary it at first and exponentially increase rollout from thereon. Any initial error should have meant a halt in further deployments.

      Canary isn’t the only way to solve it, by the way. Just an easy fix in this case.

      Unfortunately what is likely to happen is that they’ll find the poor engineer that made the commit that led to this and fire them as a scapegoat, instead of inspecting the culture and processes that allowed it to happen and fixing those.

      People fuck up and make mistakes. If you don’t expect that in your business you’re doing it wrong. This is not to say you shouldn’t trust people; if they work at your company you should assume they are competent and have good intent. The guard rails are there to prevent mistakes, not bad/incompetent actors. It just so happens they often catch the latter.

      • dfyx@lemmy.helios42.de
        0·
        6 months ago

        Filezilla itself is not the problem. Deploying to production by hand is. Everything you do manually is a potential for mistakes. Forget to upload a critical file, accidentally overwrite a configuration… better automate that stuff.