• 🇨🇦GreenBeard🇨🇦@lemmy.ca
    link
    fedilink
    English
    arrow-up
    70
    ·
    6 hours ago

    I don’t see why it would be a problem. It’s the ultimate expression of the core values of the company. An archive for all time of all of human knowledge needs a stable, knowledgeable pool of well informed archivists that are going to keep that mission on track long term. You would think that they’d WANT the workers to unionize if only to ensure the project can sustain itself.

  • GreenKnight23@lemmy.world
    link
    fedilink
    English
    arrow-up
    34
    ·
    5 hours ago

    all tech workers should unionize. we are a skilled workforce that is currently being targeted by big tech money.

    • 🇨🇦GreenBeard🇨🇦@lemmy.ca
      link
      fedilink
      English
      arrow-up
      11
      ·
      4 hours ago

      There’s limits to that. It’s hard to unionize things where the job description isn’t fairly stable. There’s lots of areas where we could and should unionize, but if you can’t define a professional standard of competence as a worker, it gets very messy to define a membership base. That doesn’t mean there aren’t mature disciplines within the field that absolutely should unionize, but “All” gets a bit… fuzzy.

      • GreenKnight23@lemmy.world
        link
        fedilink
        English
        arrow-up
        11
        ·
        3 hours ago

        I’m pretty certain all tech work is very well described. silos exist for a reason. if anything, unionizing would force shitty companies to adequately describe what job they are hiring for instead of looking for “rockstars only” or my favorite “family members”.

        those are just flag words for “we’re going to hire you for this, and make you work on anything but that for 18 hours a day until you quit”

        • 🇨🇦GreenBeard🇨🇦@lemmy.ca
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 hour ago

          “All tech work” is very much not well described, since by its nature, we tend to exist in a bubble on the bleeding edge of developing industry, where there is no broad standardization and best practices that worked as little as 2 years ago, are now not only obsolete, but can have catastrophic consequences. While there’s certain fundamental principles that tend to hold, the specifics of any two tech jobs are often wildly different. I’ve watched way too many seasoned professionals, step into a new roll at a different company and end up crashing out within a week because in spite of having some similar characteristics, they were in no way qualified to be doing what they signed up for. The ground moves too quickly here for us to even define “tech worker” in a lot of cases. Is an accountant with above-average VB skills a tech worker? A particular super-user in an engineering firm, are they a tech worker? Certifications expire on short intervals for a reason.

          • GreenKnight23@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            45 minutes ago

            I think you’re confusing skillset and technology with roles and positions.

            electricians are unionized even though there are like 300 different standards across different states, counties, and municipalities. they understand the core of their job and build off from that. same can be done within tech. DBAs, developers, ops, security, etc. hell even call support can be unionized.

            there wouldn’t be one “tech worker” union, but multiple specialized unions to cover targeted roles.

  • Artwork@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    4 hours ago

    Thank you for keeping the ineffably marvelous history intact as much as possible!

    Let’s hope it’ll help the following issue of HTTP 429 (i.e., “rate limit”) I do get frequently, too (e.g., ~7/10 times), for unknown reasons, possibly originating from the relatively recent update:


    Source