It’s getting more and more unhinged on LinkedIn.

  • Red_October@lemmy.world
    link
    fedilink
    arrow-up
    32
    ·
    8 days ago

    This really implies a level of competence and understanding among the highest levels of management that I think we all know just isn’t there.

    • pivot_root@lemmy.world
      link
      fedilink
      arrow-up
      11
      ·
      8 days ago

      Rust is one of the harder languages for beginners to learn because of its borrow checker and strict ownership model, but it shouldn’t take more than a month or two for a competent senior to pick up.

      It’s going to be deeply unpleasant and seem like a problem if:

      • You’re writing dangerously bad C or C++ code already.
      • You’ve only ever used Python or JavaScript.
      • You try to shoehorn OOP and inheritance into it (Rust idioms are composition and functional programming).
      • You refuse to use/learn pattern matching.
      • You’re a pedant about “pretty” syntax.

      If someone is at a senior level and any of those apply, they probably shouldn’t be at a senior level, though.

      • barsoap@lemm.ee
        link
        fedilink
        arrow-up
        5
        ·
        edit-2
        8 days ago

        You’re a pedant about “pretty” syntax.

        Oh I’m definitely whinging about it but it doesn’t make me stop using Rust. People coming from C or especially C++ don’t really have a leg to stand on, though, neither do people coming from ML. It’s Haskell people who get hit hardest.

      • Jocarnail@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        8 days ago

        I’m still learning Rust coming from Python and R and honestly point 2 and 3 are not even that bad. Sure I have been bashing my head against some corners, and the lack of OOP was somewhat unexpected, but imho the language really helps you think about what you are doing.

  • vii@programming.dev
    link
    fedilink
    English
    arrow-up
    9
    ·
    8 days ago

    This is triggering me really good. Especially the part about seniors competing with juniors. Has this person ever met … people?

  • *dust.sys@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    8 days ago

    This whole circumstance just reminds me of COBOL. Nowadays you have scant few programmers for it, but the ones who do demand a big salary because it’s such old specialized technology and often they have decades of experience in it. There’s simply less COBOL programmers than there were in the languages heyday, and the ones trying to enter that market nowadays have a huge learning curve ahead of them.

    The only reason most of these places that do that though, is because they wrote in COBOL to begin with decades ago, and didn’t want to switch away to something more modern as other languages gained functionality and popularity.

    I doubt C is ever going to go the way that COBOL has, it’s too ubiquitous, but it does make one consider the language you write in and how compatible it may be not just with what exists today but what’s going to exist years from the creation of that code.

  • peregrin5@lemm.ee
    link
    fedilink
    English
    arrow-up
    6
    ·
    8 days ago

    Bruh. Just put Rust on your resume. It’s not like they’ll actually check and you can still Google everything.

  • SoftestSapphic@lemmy.world
    link
    fedilink
    arrow-up
    5
    ·
    8 days ago

    The US government spending tens of millions of dollars funneling every student into STEM for the last 20 years was absolutely a coordinated attempt to drive down the cost of that labor.

  • Eager Eagle@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    8 days ago

    Here’s a shocking (/s) observation: it’s about different things for different people.

    For seniors like the author, it may be about companies trying to replace them with cheaper professionals. For companies, it may be about renewing the workforce. For product owners / tech leads, it could be about the opportunity of using a rewrite to pick a stack that better aligns with the problems they’re trying to solve. For regulators it may be about its safety features and eliminating entire categories of common issues. For juniors, it may be about choosing a language they actually like working with.