4 ms·
At all places I've worked at, it's been the "jump in the water and try to swim" technique. One thing really helpful is stressing the importance of asking questi
by shogun21 11y ago
At all places I've worked at, it's been the "jump in the water and try to swim" technique. One thing really helpful is stressing the importance of asking questions, even if they're dumb/simple.
Code reviews are also really helpful. We use a projector and go through pull requests line-by-line, asking questions and explaining design decisions.
Acknowledge the fact that it's going to take long time and just keep new programmers bouncing around with projects so they eventually touch all areas of the code base.
- thumbtackthief 11y agoSadly, while question-asking is encouraged, question-answering is not. I can't count how many times I've asked something--to the group as a whole or to an individual--and it's just been ignored. Do you find the "sink or swim" the best technique, or just the way it's done?
- shogun21 11y agoDoes everyone have someone they know they can go to for questions? I've had times where asking a question to a group, it could be ignored (everyone assumes someone else will take care of it). But if you can have a one-on-one with someone, I haven't had those instances ignored. That's just how it's been done. I do think, though, the best way to learn a system is to work on internal, non-critical projects.
- thumbtackthief 11y agoWe're a small team, but just today I was in the middle of a Slack chat with someone and told him I was lost, but never got a response.