There’s a shortage coming that nobody’s put on a slide yet: senior engineers. Every company on earth is about to want one who can drive a fleet of agents with judgment — and almost nobody …
  • Klear ( Klear@piefed.world ) English
    71·
    6 days ago

    I tried reading the article, got about halfway through and it just keeps repeating the same thing over and over again. It starts with this:

    There’s a shortage coming that nobody’s put on a slide yet: senior engineers. Every company on earth is about to want one who can drive a fleet of agents with judgment — and almost nobody is making new ones anymore, because AI ate the entry-level work juniors used to learn on

    That’s it. That’s the whole article as far as I was willing to read. There’s almost no extra information further down. Holy hell.

    • username_1 ( username_1@discuss.tchncs.de ) 
      22·
      6 days ago

      Typical modern article. And then some people are going angry “You obviously have read only the title, not the article in full”. Wonder why people limit themselves only to titles? Maybe because the article is 2 sentences worth of data fit into 20 paragraphs of the life story of Jane Smith who was amazed and sat in awe after reading e-mail that will change her life?

  • ExLisper ( ExLisper@lemmy.curiana.net ) 
    16·
    5 days ago

    There’s a terrific writeup from the folks at FlintAI — their team is now 5 devs and 45 agents, all living in Slack. Nine agents per developer. The agents take roles — triage, deploy, review — the human steps in for the two decisions that actually matter (code review, release approval), and they report something like a 3x productivity bump. It’s a genuinely impressive piece of engineering and you should read it.

    That’s the model everybody’s racing toward right now: take your best seniors, strap nine agents to them, and harvest the multiple. And it works! I’m not knocking it (and I’m doing it too)!

    I’m a senior but if the future of my work is reviewing AI code all day I will buy a bunch of goats and become a goatherder.

  • annoying_cyclist ( annoying_cyclist@programming.dev ) 
    5·
    5 days ago

    This post is the piece those two were circling around: what happens to the bottom of the chart, and whose job it is to fix it. Spoiler — it’s yours, senior engineer. It’s mine. And most of us are about to get it wrong in a very specific, very tempting way.

    BS. Most good seniors I know would love to hire more juniors, feel badly for the mass of recent college grads who are unemployed, and enjoy mentoring new engineers without needing a wall of AI slop to tell them to do so. When you give us control over the hiring budget and let us hire juniors again, you can blame us for the future senior engineer shortage. Until then, blame the people actually at fault (management, executives, the investor class), not us.

  • Farooq ( farooqkz@realbitcoin.cash ) 
    4·
    5 days ago

    Everyone thinks LLMs boost productivity. But from psychological point of view, the developer being both the subject and the object is no where near scientific and reliable.

    In other words, the developer who is using the LLM also reports they are productive. But humans can rarely be good judge over themselves. That’s why we’ve got therapists. So we have to wait for some serious and well done research if LLMs boost productivity.

    Another concern I have which prevents me from using LLMs, is the unknown long term effect on the codebase. You know, writing something is much easier than maintaining it for years after years. And every decision you make, you must be mindful of this. So I’m gonna wait and see what’ll happen after 1-3 years to the softwares with heavy LLM assists. Will their codebase still be easy to maintain?