Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
rutee071098162dMaybe he's just more exposed to that task. When I was a junior developer, I have tasks that seniors don't do. Their tasks are more complex than mine but they take a while to do my task or resolve issues related to it because it's not something they do on a daily basis and they are not familiar on where things are.
You should be able to figure it out but the speed doesn't mean anything unless you're both exposed in a new codebase with tools unfamiliar to both of you.
Oktokolo75362dYou saw what you expected to see, not what actually was there. It is a common problem of authors, engineers, coders... everyone who works creatively but creates stuff that has to follow some rules.
There is nly one solution to that:
Interrupt debugging with some other mentally demanding task to clear your natural neuronal network's internal assumptions about the code.
hah, i was in the position of that junior a few times. it's always a struggle to decide "okay, i'm gonna chime in even it's going to make the senior angry/deppressed/whatever" :)
NoMad342962dThey'd be more than happy to help. They'd feel like they have finally worn the "grown up pants" now. 😛
... And they would totally panic if they got it completely wrong, so they have that insecurity too.
AlmondSauce845462d@rutee07 is bang on, but to add - bring a senior isn't about solving things faster / better etc. than juniors. It's about the experience required to spot bad "solutions" before they become an issue, make long lasting and positive high level design decisions to drive a project forward, make helpful suggestions about the many different ways a problem might be solved, etc.
If it was just about being able to do everything better than the juniors, most seniors would lose their title very quickly, myself included.