• uis@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      4 months ago

      There is always shortage of highly-skilled unpaid labour.

  • Doubletwist@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    Not only is “Googling” one of my most important job skills, now that I’m doing professional services, my entire job basically consist of “Learn product ${FOO} faster than the customer’s employees can.” Which of course primarily consists of knowing what to search for, how to find it, and how to interpret and use what I find.

  • xmunk@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    Knowing when to cut your losses swallow your pride and ask for help is legitimately an incredibly important dev skill. I’ve met otherwise decent developers that could disappear in a hole for a month on a simple problem that anyone else on the team could help them work through in a few hours because they didn’t want to look dumb.

    • Aviandelight @mander.xyz
      link
      fedilink
      arrow-up
      0
      ·
      4 months ago

      I’m torn about this because I have good mentors but I genuinely want to try to learn how to code and not just have the answers given to me right away. At least I’m only working on volunteer project so being slow isn’t really holding anyone else up.

      • xmunk@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        4 months ago

        Don’t be torn - solve it yourself until you can’t! It’s not helpful to be someone who constantly runs to other folks to fix their stuff and neither is it good to be someone who will just frustrate themselves struggling without progress.

        If you’re a junior developer you will probably get time boxed tickets, just try and catch yourself if you’re spinning your wheels (and that isn’t easy, it takes practice).

        As with most things in life balance is important, you don’t want to be at either extreme.

  • nieceandtows@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    When I interviewed junior devs for my team, I had zero theoretical questions, and only two coding questions which were basically code that had to be debugged, and once it was running, for them to implement some minor things that I asked them to implement. I said I don’t mind if they googled, I only wanted them to share their screens while they worked, so that I can see how they worked and how they googled/adapted the answers to their code. I interviewed over a dozen people ranging from freshers to 4 yoe, and you should see how terrible they were at googling. Out of all them, only one fresher came close to being good in the interview. Even ‘4 yoe’ devs who ‘spearheaded’ various projects sucked at basic python and googling.

    • Aquila@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      4 months ago

      I would 1000% become dumb as a rock with someone watching me not to mention in a high risk setting such as an interview

      • MajorHavoc@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        4 months ago

        Yeah. We do a ton of screen sharing guided mentorship in my role, and everyone can’t think straight while sharing their screen.

        We get through it, and feedback says it’s worth it. But it still sucks in the moment.

      • fsxylo@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        I tend to do the most embarrassing sitcom shit possible when someone is watching me do something I’m an expert in.

  • Olhonestjim@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    I put “Simple Green” on my resume skills section. Cleaning isn’t a huge part of the job, but I knew they used that specific brand across the industry.

    The interviewer mentioned it with a laugh. I got the job.

  • jubilationtcornpone@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    “Prompt Engineering”: AKA explaining to Chat GPT why it’s wrong a dozen times before it spits out a useable (but still not completely correct) answer.

    • lad@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      If there exists an answer, as gpt will tell you the answer exists till the very end, even when it’s not so

    • ByteOnBikes@slrpnk.net
      link
      fedilink
      arrow-up
      0
      ·
      4 months ago

      That’s actually a valid skill to know when to tell the AI that it’s wrong.

      A few months ago, I had to talk to my juniors to think critically about the shitty code that AI was generating. I was getting sick of clearly copy-pasted code from chatGPT and the junior not knowing what the fuck they were submitting to code review.

      • pfm@scribe.disroot.org
        link
        fedilink
        arrow-up
        0
        ·
        4 months ago

        I’m trying to convince a senior developer from the team I’m a member of, to stop using copilot. They have committed code that they didn’t understand (only tested to verify it does what it’s expected to do). I doubt it’d succeed…

        • odelik@lemmy.today
          link
          fedilink
          arrow-up
          0
          ·
          4 months ago

          Co-pilot is amazing and terrible at the same time.

          When it’s suggesting the exact line of code I expect to write, amazing. When it can build the permissions I need for a service account for a TF module I’ve written, amazing

          However, it will suggest poorly formed, un-optimized code all too often.

          That said, knowing when to use/not use/modify the suggested code has greatly improved my productivity and consistency.

      • Evotech@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        4 months ago

        Should start asking them like, why did you do this? Why did you chose this method? To make them sweat :p

        • lad@programming.dev
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 months ago

          That used to make sense when LLMs were not the thing, when evaluating assessments from students, half of which asked someone else and didn’t bother to even read the code

          • howrar@lemmy.ca
            link
            fedilink
            arrow-up
            0
            ·
            4 months ago

            If no one can make sense of the change, then you reject it. Makes no difference if it was generated with an LLM or copy-pasted from Stackoverflow.

  • njm1314@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    I have so many weird things on my resume just because that’s what job descriptions ask for. Like 10 job descriptions I was applying to ask for number key skills, which doesn’t seem like a skill to me but if they want it on there I got to have it on my resume or I won’t get an interview

    • funkless_eck@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      4 months ago

      I leave space in my resume template, and every job I run through chatgpt for a list of skills. Add them in, spin up a cover letter same process and send.

  • Th4tGuyII@fedia.io
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    To be fair you could call this “search optimisation” and the people on Linkedin would eat this up