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 …
  • anon_8675309@lemmy.world
    22 days

    Stop hiring and mentoring junior engineers and you’ve quietly unplugged the machine that makes senior ones. A few years out, you run dry — right when everyone else is dry too, and the price of the few left goes through the roof.

    Written by AI

  • HaraldvonBlauzahn@feddit.org
    22 days

    You Can’t Just Buy Them

    I can hear the objection, because it’s the obvious one and I’ve made it myself: just hire seniors when you need them. Let the other guy train them. Poach the finished product. It’s cheaper, it’s faster, and it has worked for the entire history of this industry. Right? WRONG.

    Here’s why that breaks: everyone is about to have that exact same idea at the exact same time. Every company that quietly decides juniors are too expensive is also quietly deciding to buy its seniors on the open market later.

    One might think that companies really ought to be smarter. But the histories of whaling and fishing shows that profit-oriented industries are absolutely capable of completely and irreversibly wrecking their own economical foundations for a few years with a bit of extra profit.

  • Klear@piefed.worldEnglish
    22 days

    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.

    • Logi@lemmy.world
      21 days

      Yeah, that was probably the prompt. More or less. Then it’s padded with a mountain of slop.

    • username_1@discuss.tchncs.de
      22 days

      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?

      • MalReynolds@slrpnk.netEnglish
        22 days

        I tend to just look at the comments first here for anything even slightly questionable. Seems like some of the dumbed down shit does actual brain damage to read.

      • biofaust@lemmy.world
        21 days

        Typical modern book as well. I keep reading classic philosophy just for being amazed at the amount of concepts crammed in under 100 pages.

        • username_1@discuss.tchncs.de
          21 days

          Never read modern philosophy, but I had completely opposite experience with mid-late XIX century philosophy: too much words and too much repeating of the same thought from too many different angles. But I’m a technician type of guy so I might just have been unlucky with the set of authors. Never cared to read much of philosophy.

    • HaraldvonBlauzahn@feddit.org
      22 days

      Bert Hubert wrote about the same consideration in a blog post.

      I think the consideration itself is valid. But Berts position has a big difference: He does not pretend that he can tell the future. It is quite logical and to expect that people ceasing to work as junior developers, or them not finding a job, might lead to a scarcity of senior developers. But we do not really know what happens. I’d describe it more as the whole field in crisis. And the jobs that remain, might not be the jobs that experienced senior developers, of which e.g. in Germany purely by demographics many are close to retirement, really want to do.

      Something similar, at a perhaps smaller scale, has happened during and after the Corona pandemic in Europe in the field of hospitality: People in this sector could not get work, or only short hours. So they left the field, since there were other, better paying jobs, with more friendly work times. Hotels and restaurants experienced a worker shortage. One could have expected that then, the businesses had to pay more to attract people. But this did not happen at a significant scale. Was happened was automation and reduction of work, lowering of service standards, and restaurants closing. Was this predictable? I do not know.

    • criss_cross@lemmy.world
      22 days

      Was gonna say I took a pay cut and I’m staying at my current braindead job right now because the market is ass.

    • locuester@lemmy.zipEnglish
      22 days

      The graph is anticipating the future. Not current. Take a couple years off.

      • boaratio@lemmy.world
        22 days

        My family had just bought a house before I was laid off, and we’re burning through our savings at an alarming rate. If I don’t find a job soon, I’m going to have to liquidate my retirement account. I don’t have years, I have months.

      • grue@lemmy.world
        22 days

        But if you take a couple of years off, won’t it be tough to get back in?

        • locuester@lemmy.zipEnglish
          22 days

          No one knows.

          I think a true Sr shortage is likely decade+ away. So if you need money you gotta make ends meet somehow.

          I’m leaning into the AI space, becoming proficient at understanding and developing harnesses for different purposes, running local models, adjusting to context switching more often than not, etc.

          I’m currently working a short term AI Cyber gig for a financial firm I already had a relationship with, but then taking time off to tinker.

          Dev/Sys/Net Operations, Cyber. All great fields for leaning into AI

  • ExLisper@lemmy.curiana.net
    21 days

    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.

    • Randelung@lemmy.world
      21 days

      I’ve already started rebelling. That won “efficiency” is in part mine, I’m just going home. Why would I allow my bosses to reap all of the rewards for my shittier workday? And if they don’t agree, I’m going back to writing by hand.

  • absquatulate@lemmy.world
    22 days

    So soon? I figured it’d take a couple years for them to realize how they shot themselves in the foot by not hiring juniors anymore.

    • boonhet@sopuli.xyz
      22 days

      It’s fucked and it has been for a while now. You see, you currently put yourself at a disadvantage if you DO hire juniors because later down the line others will just poach them from you. You’ll be lucky if they ever turn into a net positive for your country.

      Only way this changes is if most big companies that can take the budget hit start hiring juniors again. Fat chance of that right now.