• nthavoc@lemmy.today
    link
    fedilink
    English
    arrow-up
    4
    ·
    2 hours ago

    That’s a red flag that the managers have no idea what they are asking for and have no idea what it is they make. They just know the last person that probably up and quit to go be a in a completely different career was the only person that retained that knowledge.

  • WrenFeathers@lemmy.world
    link
    fedilink
    arrow-up
    40
    arrow-down
    1
    ·
    8 hours ago

    Serious question:

    Why is their name blurred when they openly stated they are the one that created the product?

    A quick search shows exactly who they are?

    I’m serially trying to understand if this is an etiquette in the industry, or something? I’m admittedly ignorant when it comes to tech.

    • AdrianTheFrog@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 hours ago

      It’s a common internet thing that’s probably mostly done just out of habit, it doesn’t have any purpose like 90% of the time, but is generally the standard just for those few times where it might actually help

    • spicehoarder@lemm.ee
      link
      fedilink
      English
      arrow-up
      9
      ·
      6 hours ago

      It’s the whole anti brigading thing. But I think if you’re dumb enough to post an ass take in public circles, you deserve the heat. Mods just make it a blanket rule to blur out names so they don’t have to actually read anything lol

  • Skasi@lemmy.world
    link
    fedilink
    arrow-up
    128
    arrow-down
    5
    ·
    12 hours ago

    Does it make sense to blur names when they’re still relatively easy to decipher, when the project can be found on github and the top committer links to their Twitter account? 🤔

  • Soup@lemmy.world
    link
    fedilink
    arrow-up
    22
    arrow-down
    2
    ·
    11 hours ago

    My friend works as a Unix admin and his older coworker, who is paid way more than he is, is essentially useless and always slowing everyone down. Constantly asking basic questions and getting stuck on simple things for a whole day when he doesn’t ask.

    Same with driving. I don’t care how long you’ve been doing it if you haven’t put any serious effort into learning and improving after passing your pathetic, weak test 38 years ago.

    • catfrog@lemm.ee
      link
      fedilink
      English
      arrow-up
      8
      ·
      9 hours ago

      No shame in asking questions

      Tech fields are always moving forward, if someone has a question they should ask instead of guess

      Further, older entrants with experience in older technologies have value that a company may need that newer entrants may not have really had the opportunity to ever work with. Deprecated technology still runs a lot of systems and companies will drag their feet in moving on because they have these older people working for them that, if a problem comes up they’re going to deal with and the company perception is that it’s cheaper than updating the entire thing to more modern solutions.

      • Soup@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        8 hours ago

        Oh I should be clear that this person is absolutely a problem. They’re far less effective at their job, don’t learn for long after the question is asked, and the value they bring to the team is, in some ways, less than a fairly young person. And yet they’re paid more because “experience”.

        I have the same thing in my field(architecture and structural engineering firms) as a technologist. People who refuse to learn new skills with the software constantly hold back people willing to put in the effort.

    • AdolfSchmitler@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      8 hours ago

      I feel like this is almost every company ever. Incompetent people near the top being propped up by lesser paid people doing all the work.

  • jol@discuss.tchncs.de
    link
    fedilink
    arrow-up
    3
    arrow-down
    6
    ·
    edit-2
    11 hours ago

    Who asks for years of experiences of fastAPI? That’s so weirdly specific. I doubt this story is real.

    • stankmut@lemmy.world
      link
      fedilink
      English
      arrow-up
      19
      ·
      11 hours ago

      Job posting requirements are done by a game of telephone where each person down the line is less technical than the previous.

      A manager is able to hire a mid-level engineer, which their company defines as 4+ years of experience. An engineer tells the manager what technologies they use, bringing up fastAPI at some point. The manager then gives this list to someone who writes up the job posting who just puts ‘requires 4+ years’ on every bullet.

      Nearly every job posting that asks for more experience than is possible or for something weirdly specific happens this way.

    • mindaika@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      3
      ·
      9 hours ago

      Nah, I’ve seen it. I just went through the whole job hunting thing again, and the main thing employers want (I’m a Data Engineer) is many years of experience using their specific tech stack. 5 years with dbt. 10 years with Snowflake. 6 years with FastAPI… and so on.

      • jol@discuss.tchncs.de
        link
        fedilink
        arrow-up
        2
        ·
        7 hours ago

        I guess there’s lots of idiots hiring. We definitely state our specific stack as a bonus, but expecting candidates to be these magical unicorns that know exactly what you need… It’s so insane. I much rather hire someone motivated to learn.