• seth@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    Laying people off instead of offering to move them to the now-more-important projects has to be one of the dumbest management moves that tech companies repeatedly do. These are people already trained on all the policies and procedures and tooling and “culture” specific to your company.

    It’s going to be more expensive to hire and train new people when the dumdums in upper management finally figure out the mistakes they made that got them to a point where they decided they need to cut jobs and projects, and the ramp-up time before you actually start seeing progress on those priorities is going to be seriously lengthened. Of course they won’t acknowledge it was their fault in the first place, and again the heads roll on the wrong end of the corporate ladder.

    • burlemarx@lemmygrad.ml
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      It’s not dumb. They understand what they are doing. They think firing multiple people at once can flood the market with developers, and the situation could be used to hire new people with a lower compensation.

      Don’t think the rationale behind this is work quality or developer productivity. This is a power move. For Google and many big tech companies devs are replaceable and are just cogs in the machine. The problem is that they became too costly with the advent of COVID.

    • boyi@lemmy.sdf.org
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      It’s going to be more expensive to hire and train new people when the dumdums in upper management finally figure out the mistakes

      Unfortunately that’s not the case. Those who have been laid off are those paid high salaries to build up the foundation. Now that the foundation is already there, they future work won’t be as complex as before and need less training. So why would they still pay the very high salaries? They’ll just get rid of the used-to-be-important programmers and hire the can-be-hired-for-a-lot-less programmers from India. It’s sad, but that’s the reality.

      • Maddier1993@programming.dev
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        5 months ago

        Now that the foundation is already there, they future work won’t be as complex as before and need less training.

        LOL, LMAO even.

        • boyi@lemmy.sdf.org
          link
          fedilink
          arrow-up
          1
          ·
          5 months ago

          Yeah, at least give you argument so I can also laugh at myself too.

          Anyway, take a look at this article that just came out just earlier, which means that by no chance it’s been referenced when I wtote my earlier comment. And do take note of the BOLD words.

          The Core unit is responsible for building the technical foundation behind the company’s flagship products and for protecting users’ online safety, according to Google’s website. Core teams include key technical units from information technology, its Python developer team, technical infrastructure, security foundation, app platforms, core developers, and various engineering roles.

  • ericjmorey@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    Disinvestment into Python, Flutter, and Dart is a clear signal that those tools are unimportant to Google. I won’t be recommending that anyone use Dart or Flutter on new projects.

    • DeprecatedCompatV2@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      I won’t be recommending that anyone use Dart or Flutter on new projects.

      You seem to think Google cares at all. Android has been languishing and Flutter is lightyears ahead. KMP is junk compared to what Flutter has accomplished with a fraction of the bells and whistles.

      • ericjmorey@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        You seem to think Google cares at all.

        Odd conclusion to draw. I’m simply not inclined to recommend tools that are not going to be supported by the organization that created them. Development ecosystems are important when planning a project.

        • DeprecatedCompatV2@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          5 months ago

          What I mean to say is that Google isn’t invested in native android either. It’s been repeatedly strip mined by first-timers looking for a quick promotion and left to burn.

          Things got so bad that Google gave up on native Views and created Jetpack Compose, which has been a source of many complaints related to performance.

          In 2024 Flutter has instant hot-reload, and the “native” (but 100% bundled) solution still requires a complete reinstall on the device. In fact, Dart can compile to native code (or JIT) without an issue, yet Kotlin Native is barely in GA in the new compiler support has been lagging while the new compiler isn’t out of beta and is still poorly supported by tooling.

          Consider the absurdity: React Native is the only true native framework out of RN, Jetpack Compose, and Flutter. And all of this barely scratches the surface of the tooling problems that Flutter 99% avoids by allowing development on desktop, web or iOS simulator.