I started working for a big corporation about six months ago. Turns out a few months before I started there was a new CTO hired from a startup. This CTO has been on a hiring spree and basically hired all of the technical staff of the startup he came from (to the point that they’re suing the company I work for).

All these people from the startup have their own office, away from all the corporate offices. And they’re writing something (that they won’t reveal) in what they refer to as their bunker. The best we can gather is that they’re coming up with modern equivalents of all the backend services. This would mean that everything the devs do in the office I work in will be redundant.

I have the feeling that within a year or so (maybe less) there’ll be mass layoffs of all the existing devs. Am I being paranoid?

    • wicked@programming.dev
      link
      fedilink
      English
      arrow-up
      20
      ·
      1 year ago

      Yeah. Everything depends on the complexity of the product, but it’s just as likely that it’s the new CTO and his team that gets canned when they get bogged down in the details and the costs start racking up.

      • V699@kbin.social
        link
        fedilink
        arrow-up
        7
        ·
        1 year ago

        Startups inside companies usually get shut down once the bill gets too high. I’ve experienced this first hand

    • buxton@programming.devOP
      link
      fedilink
      English
      arrow-up
      14
      ·
      1 year ago

      This may be the case. They’ve gone from “this should be easy” to “oh, we never thought about that” pretty quickly.

      • nephs@lemmygrad.ml
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 year ago

        That screams inexperience in their end, to me. 20 years in the field, I learned to respect legacy. Can’t move away from it without getting it under control first and then weeding out the smelly parts.

    • BaconIsAVeg@kbin.social
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      The biggest problem with that approach is your team loses their roadmap, funding for new initiatives, and ambition while that’s happening. Your sprint backlog has nothing but minor tech deficit tickets in it, and overall it becomes a chore to get anything done.