• sugar_in_your_tea@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    13 days ago

    That’s our architect, and they’re not a dev (they don’t even do code reviews), but they are quite critical because it’s their job to understand the entire app, including in-progress changes from other teams. They have their own team (architecture), so they don’t report on any dev team, they report to the director.

    Maybe that’s what others are calling a “lead dev”?

    • TheRagingGeek@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      13 days ago

      Seems to be a trend, my boss was telling me that the VP’s in our org think we need more lead devs and less solutions architects, though they would functionally be doing largely the same role, meetings, planning, design, interfacing with teams they are dependent on, annual technology reviews etc. I think it’s going to bite them in the end

      • sugar_in_your_tea@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        ·
        12 days ago

        I imagine hiring will be an issue. Devs want to dev, and naming an architect role a “dev” role doesn’t communicate the role properly.

        • TheRagingGeek@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          12 days ago

          Yep, they talked about it a bit during my hiring what I wanted my title to be since they are paid the same and do the same tasks(in addition to some coding expectations). I’m glad I chose architect, but ultimately they squeezed me out of that with RTO mandates for architects and above.