It was to talk about “team restructuring”

  • JackbyDev@programming.dev
    link
    fedilink
    English
    arrow-up
    25
    ·
    1 year ago

    No one knows how to use a well documented, publicly available service? No, I’d argue that no one knows how to use a private, internal only, custom solution.

    • Ajen@sh.itjust.works
      link
      fedilink
      arrow-up
      19
      ·
      edit-2
      1 year ago

      That because you’re an engineer (I assume). The people signing off on these kinds of projects don’t know enough themselves, so they go to someone they trust (the old timers) to help them make the decision. The old timers don’t keep up with new tech, so we keep reinventing the wheel.

      • BoofStroke@lemm.ee
        link
        fedilink
        arrow-up
        11
        arrow-down
        1
        ·
        1 year ago

        “keeping up with new tech” is often just re-inventing the wheel. If it isn’t broke, and can still be maintained, then why break it because you like the flavor of the week?

        • Ajen@sh.itjust.works
          link
          fedilink
          arrow-up
          8
          ·
          edit-2
          1 year ago

          In this case, we’re talking about the OPs example of someone implementing a complex message passing architecture in Java instead of using an off the shelf solution. There are devs with 20+ years at the same company who don’t know the basics of networking/cloud, because they haven’t improved their technical skills much in those 20 years and instead focused on corporate politics. Those are the people who tend to gets asked for advice from upper management.