I have been working at a large bank for a few years. Although some coding is needed, the bulk majority of time is spent on server config changes, releasing code to production, asking other people for approvals, auth roles, and of course tons of meetings with the end user to find out what they need.

I guess when I was a junior engineer, I would spend more time looking at code, though I used to work for small companies. So it is hard for me to judge if the extra time spent coding, was because of me being a junior or because it was a small company.

The kicker, is when we interview devs, most of the interview is just about coding. Very little of it is about the stuff I listed…

  • Rimorso@feddit.it
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    Senior backend developer here . I have been refusing positions as tech or team lead for exactly this reason. All my colleagues that ended up in those positions basically stopped having any time to code. Some of them left to go back to coding in another company as they were burning out from all the meetings and admin stuff.

    • scottyjoe9@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      This is exactly what happened to me. I was a team lead at my old job and I interviewed as a senior dev but got offered a standard dev position. In the end they offered me the same money as what I was making as a team lead so I took it and have never looked back! The reduced pressure and better work-life balance are so good. I now earn much more than I did at my old gig so 🤷‍♂️

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

      Same boat. Nuh uh, you’re not promoting me. I don’t want to have to deal with offshore support, meeting 6 out of 8 hours, making sure Jira board is up to PM’s standards and only reading code when any of the devs have an issue they cannot solve by themselves or something breaks. I tried management career path and hated it with all my heart, quit when they wanted to promote me higher. Let me do what I enjoy, I’ll deliver.

      Bonus points - developers make more than managers up to 2 or 3 levels up where I live, so it doesn’t even calculate.

    • Feyter@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      I’m sure in a few years from now nobody will code anymore and you will just tell the AI what you want to see implemented.

      Same as nobody writes actual machine code anymore and everyone only uses higher languages.

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

        You still have to understand the code as a senior, you don’t want to merge code, where you don’t know what it’s doing (AI extinction anyone, haha?). And I actually doubt that nobody will code anymore in a few years, as some stuff requires quite some creativity that is just nowhere close with LLMs (even with GPT4). I’ll admit though that probably 90+% will be able to be written by AI (and is in some way today already, if it’s relatively repetitive code). So yeah the new main dev-role will likely be “prompt-engineer”. But it’ll be interesting, the fast progress with AI never stops to surprise. And GPT4 is definitely able to think slightly abstract (and with correction writes quite good code). Deepmind also just recently released alpha-dev, which improved the state of the art in sorting…