• bridgeburner@lemmy.world
    link
    fedilink
    arrow-up
    17
    arrow-down
    1
    ·
    1 day ago

    Nice meme from the past. Too bad nowadays corpos don’t hire juniors anymore, their work is done all by AI. Or at least that’s what corpos wish for.

  • Log in | Sign up@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    1 day ago

    I’ve had a few bosses who were great at shielding the team from shit and sticking up for the department in front of everyone. I’d do absolutely anything for them and we all pitched in because it was us.

    I applied for my current role partly because I knew who my boss would be and I knew he’d be great. He has my back and I have his. Same is true for the whole team.

  • ChickenLadyLovesLife@lemmy.world
    link
    fedilink
    English
    arrow-up
    39
    arrow-down
    2
    ·
    2 days ago

    I was fine with mentoring junior developers until my manager decided pair programming was the way to go. I’m happy to help and teach, but like fuck am I going to sit at the same goddamn computer with some maroon all day. Can’t even power-nap properly.

    • pinball_wizard@lemmy.zip
      link
      fedilink
      arrow-up
      5
      ·
      24 hours ago

      Can’t even power-nap properly.

      Yes. Pair programming should be encouraged when appropriate, not mandated.

      Naps are a part of the critical path! Lol.

    • Rooster326@programming.dev
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      1 day ago

      The entire reason we developed git was so nobody would ever have to pair program again.

      Does he also request you write the code on paper first?

    • ToxicWaste@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 day ago

      pair programming can be really cool. if you have a complex problem, are roughly on the same level as the pair, are both motivated to do it.

      that is a huge if. also the reason why it should never be mandated. suggested at most.

    • Howdy@lemmy.zip
      link
      fedilink
      arrow-up
      4
      ·
      1 day ago

      Full agree. Pair programming makes me unproductive and it’s always just feels like one person doing it and the other person in the back saying “uh huh, yeah”. Our place used it as a learning opportunity but the problem is the person I pair with haven’t ever worked on my project and have no clue what’s going on when I’m month deep into a feature branch.

    • fruitycoder@sh.itjust.works
      link
      fedilink
      arrow-up
      17
      ·
      2 days ago

      Pair programing with a mentor shouldn’t be a day to day thing. Like why waste the time and put so much pressure on the trainee like that anyways?

      • epyon22@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        15
        ·
        2 days ago

        Honestly pair programming I feel works better with more similar abilities than far off. Also give em a task to let them struggle a bit in the beginning of the sprint.

  • FreshLight@sh.itjust.works
    link
    fedilink
    arrow-up
    33
    ·
    2 days ago

    Middle management is also there to communicate both ways in order to manage expectations. Especially when the senior dev is busy as well. And ideally the first few weeks to months after onboarding are there for junior devs to train and to get comfortable with the new environment (programmatically and socially). I get a lot of anti-work vibes from Lemmy communities, and while I get that capitalism is bad and big corps are optimizing profits over the employees’ well being, I also think that work doesn’t necessarily have to suck. I mean, it’s pretty neat when someone’s good at a thing and gets paid for doing something they somewhat like and are good at 70% of the time.

    If times are rough and you have to take what you can get, that’s obviously shit, though…

  • aaaaaaaaargh@feddit.org
    link
    fedilink
    arrow-up
    58
    arrow-down
    1
    ·
    edit-2
    2 days ago

    That is, until Sr. Dev is forced to babysit AI producing PR slop all day while Jr. Dev is looking for a new job.

  • eletes@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    20
    ·
    2 days ago

    My internship manager was great at giving me challenges that were tough but achievable. I took their offer even though it was low for a fresh engineer because that team was so great to work with

  • pedz@lemmy.ca
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    2 days ago

    I’m doing tech support and customer support. The dev team missed their deadline on the launch of the new ERP and launched it anyway a few days later. There are still Lorem Ipsum in some places. We can’t even edit client’s names or phone numbers yet. We also can’t open new accounts for a handful of clients.

    I usually can cover for “my” team. We all make mistakes and sometimes things are not going according to plan. But so far it’s the worst deployment I have ever seen. I gave up on trying to help clients and I’m now just telling them I can’t do anything, while the dev team is telling me they are working on those issues and they should be fixed “in the following days, bro”. It’s been two weeks of “this is gonna get fixed soon” while I am bullshitting the clients telling them “oh I’ve been told it would work now, please try again”.

    I’m tired and they should be better. I just script for fun. I was doing PHP 20 years ago and still host a few services for a handful of people, and sometimes I think I might do a better job than some junior programmers.

    • CrypticCoffee@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      5 hours ago

      Wait? They didn’t test it and didn’t delay when they knew it wasn’t feature complete? The failure wasn’t with junior devs.

  • idriss@lemmy.ml
    link
    fedilink
    arrow-up
    3
    ·
    2 days ago

    Well, that wasn’t my experience when I was a junior, every failure was blamed on me, PR is deliberatelty stretched to look like I am slower and worse than I am, it was a lot of suffering but we all have to start from somewhere.

  • TrickDacy@lemmy.world
    link
    fedilink
    arrow-up
    7
    arrow-down
    7
    ·
    edit-2
    2 days ago

    Pretty much. We had the worst junior dev ever and he never got better for a period of two years because he was coddled and allowed to keep submitting horrible code. He was laid off, thankfully honestly, but if there weren’t budget cuts I feel like he never would’ve improved and just kept wasting everyone else’s time.

    Edit: the point I was making here is that coddling him kept from either being fired or getting better. Not sure why people cannot understand that more than one thing can be true. In this case that the dude is a horrible dev and also that management dropped the ball. I tried to teach him shit. When he didn’t improve I let my manager know how things were going. Nothing happened to him for literal years.

    And as the cherry on top here he said he was going to start some kind of businessy-sounding machine learning degree program, after he was let go in layoffs. So yeah the dude knows he sucks at coding but definitely wants in on the AI grift.

      • FearfulSalad@ttrpg.network
        link
        fedilink
        arrow-up
        12
        ·
        2 days ago

        This assumes that Jr Dev wanted to be trained, and could be trained. I’ve known some AI-brain “devs” from before AI was a thing.

        If someone can’t be bothered to read an error message, can we really be expected to teach them how to debug? Etc.

      • jj4211@lemmy.world
        link
        fedilink
        arrow-up
        7
        ·
        2 days ago

        Sometimes it just doesn’t pan out.

        Had a junior dev that basically decided he would rather try to grift through instead of doing the job. Never seen someone work so hard at trying not to work at all. Every day it was a different excuse, a different other person to point to as to why he didn’t even try to do anything that day. I think at least 7 or 8 of his grandmothers died during his tenure. And management ate it up.

        Until one day he lost track of things and blamed the manager asking him why things weren’t done. Said the manager never sent him some material and of course the manager had. Suddenly the manager believed the rest of us who had been saying he was lying for the last many months…

        The key was he was cheap and was in theory supposed to be as good as a higher paid alternative, so management would have to admit to being wrong to ditch him…

        • TrickDacy@lemmy.world
          link
          fedilink
          arrow-up
          6
          ·
          2 days ago

          “Someone represented themselves as being very interested in development and getting better at it. It’s obviously not their fault if all that was bullshit!”

      • TrickDacy@lemmy.world
        link
        fedilink
        arrow-up
        8
        ·
        2 days ago

        It is a long story but yeah it was about 80% management’s fault and 20% the fault of the dude having zero ambition. I didn’t expect this comment to get so many downvotes… it’s as though I would need to explain that I’m not entirely blaming him for continuing to be employed in a problematic manner as he was. Obviously management should have addressed the issue and didn’t, but why am I not allowed to blame a person for sucking at their job… ? If the idea is that if I thought he sucked I should have fixed it, that’s silly, but regardless I did try to teach him things. He never retained anything, so after a few months I gave up.