this post was submitted on 15 Oct 2023
1535 points (97.5% liked)
Funny
6886 readers
1482 users here now
General rules:
- Be kind.
- All posts must make an attempt to be funny.
- Obey the general sh.itjust.works instance rules.
- No politics or political figures. There are plenty of other politics communities to choose from.
- Don't post anything grotesque or potentially illegal. Examples include pornography, gore, animal cruelty, inappropriate jokes involving kids, etc.
Exceptions may be made at the discretion of the mods.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Unfortunately there are many juniors that you give the job of doing A to C, and if you come back a week later they'll report they're still stuck at job A, point 1 and didn't want to message anyone, and is something a senior can fix in 5 minutes. Even worse you message them and they just report everything is ok, they're working on it. Of course they never update the status of the project so you never know if they're stuck or just not updating.
That makes daily meetings necessary so they don't lose the entire week and delay the project. Unfortunately more senior members also get dragged in those meetings. It's a frustrating part of working with mixed teams and a "just let me code" mentality.
When I was a manager of a small team it was all junior guys. I had to hammer into their heads to message if they had trouble making progress.
A few times I got the feeling one of the guys was having issues (based on messages). So I called them up on Friday afternoon and they admitted they were way behind because they couldn't get past an issue. But they said "don't worry, I'll work through the weekend to get it done".
I told him "no, you're not working on the weekend. We'll connect on Monday morning and work through the problem together. Just let me know sooner next time so we can get you back on track quicker."
After a couple of those they got the message that it's ok to ask for help and isn't a sign of weakness and they're not gonna get fired for asking.
As a junior engineer, wish management at my last job told me that. Since our team shrunk and lost basically all of our seniors, I felt like I was walking on thin ice with all the expectations I needed to meet. And when they have to train you + give half of the department processes to you and another junior, it can be paralyzing. Didn't help that management was never around for me to ask for help too because they were too busy picking up other issues from people leaving the company in other departments. Ugh. Me being fired was always over my head
Yeah. I've gotten into the habit of checking up on junior engineers around the time they should be asking me questions. If they haven't asked me anything, I know they are lost.
While I agree that a daily standup would help with this, I feel like there's other avenues to approach this problem. If their task is to do A -> C, give them some deadlines and if they don't meet them then become more involved. Have them check in with a senior on the problem. No need to drag the entire team into a standup because the juniors can't figure it out. You can also try to build a culture of asking for help, which is difficult to do. People either think they can figure it out eventually, or they're just slacking.
There's also the very usual problem of the scope of the tasks not being well defined and many times too big, so juniors get overwhelmed and it's difficult for them to focus on small things to actually progress or identify that they are blocked.
I remember well that when I was junior and not having yet a proper notion of when to call it "I'm blocked" since many times it seems one is blocked but is not, like spending 1 or 2 days reading and understanding the code and how all things work are very legitimate things, which are needed to even know what to ask about. But other times I was actually blocked but could not understand that I was because it felt I was just trying to understand the code and was actually going in circles not knowing when to stop.
It's all a balance, but the one important thing to do is communicate about it, not just a "I'm doing it". Usually pairing with someone and take some time to explain the "thought process" and the "current understanding" helps a lot. But, a junior kinda stuck will many times not ask for that time. What I usually do is just after a daily be the one to approach the junior and ask him to pair for a while to help him, without him even asking. Many times this solves the problem.