• sugar_in_your_tea@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    17
    ·
    edit-2
    12 hours ago

    Yup. I’m a senior software dev, and some weeks I write no code at all. Sometimes that’s because I’m researching something (output is a doc a/ estimates), other times it’s code reviews, and other times I’m stuck in meetings all week.

    But most weeks I’ll write some code, even if it’s just fixing some tech debt. If someone isn’t contributing for a month, they’re definitely not doing their job.

    • Dkarma@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      7 hours ago

      Our most critical dev / solutions expert spends most weeks in meetings.

      • sugar_in_your_tea@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        ·
        3 hours 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
          2
          ·
          1 hour 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