Tag Info

New answers tagged

1

I tell them to check error messages when compilation fails. I sit and check the error messages with them. When they ask me for help, I ask if they have checked the error or not. From what you're writing, it seems like your juniors either don't really understand your solutions and aren't able to apply them in other situations that are not 100% ...


5

I find senior developers guilty of the same mistake; that's why I think this is a sign of being overwhelmed instead of "doesn't care." My reaction is always the same: When I hear "doesn't work", I ask: "What error message do you get?" (and I try to be polite). The answer will then tell me whether the person needs to vent some steam before they can start ...


3

This is a bit of a behavior modification question, but needs to be addressed in a development team environment. Do your junior developers have to do support or any type of bug fixing? Ask them how they feel when someone just tells them "I got an error" with no other information. We can avoid all the name-calling that probably goes on when they have to deal ...


17

Do not help right away. Make the junior colleague wait for at least 15 minutes, after one or two of this 15 minutes cycles, he/she will start to look at the issue on his own. Just don't say directly "wait 15 minutes", use something like "I'm busy, please let me finish x, then I help you". If you help him immediately, this is the shortest path he has for the ...


1

"When the compilation fails"... in such cases, I'd go over to them as if to help with a brand new, difficult, requires-experience error... I'd go through the basic steps of "show me" and then I would read the error message that was displayed by the compiler, and if it really was a case of do-what-the-error-message-says, I'd put on my best "you are a child" ...



Top 50 recent answers are included