Telegram says it has 'about 30 engineers'; security experts say that's a red flag - eviltoast
  • RubberDuck@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 months ago

    A point of pride sure, also a risk. Responding to incidents requires coverage. And the OT comparison was just more on the uptime requirements and redundancies than anything else.

    • dandi8@fedia.io
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      4 months ago

      It’s no more a risk than throwing more developers at it when they’re not needed.

      “Too many devs“ can, and often is, a significant bottleneck in and of itself. The codebase may simply not be big enough to fit more.

      Besides, I still don’t see what all those additional engineers would actually be doing. “Responding to incidents” presupposes a large number of incidents. In other words, the assumption is that the application will be buggy, or insecure enough, that 30 engineers will not be enough to apply the duct tape. I stand by the claim that an application adhering to modern standards and practices will not have as many bugs or security breaches, and therefore 30 engineers sounds like a completely reasonable amount.

      • RubberDuck@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 months ago

        Fair enough, we can disagree there. It’s impressive telegram pulls it off. I’d be worried for burning out people and losing them to that. And there is a lot between working flawless and buggy mess. Fixing issues in the operational system usually takes time.

        Maintenance vs new functionality. Infra vs application. A lot to spread out across.