2 ms·
> But let’s say they do start sticking junior devs back into teams again. You have the additional issue which is now senior developers have no experience worki
by emodendroket 9y ago
>
But let’s say they do start sticking junior devs back into teams again. You have the additional issue which is now senior developers have no experience working with junior devs or training people at all. When I first started working with junior devs I had no idea how to do it. I felt lost and confused. My company was just like basically “give these people something to do so they can learn something.” But that’s really not a lot to go on.
I don't really agree with this. I've had to mentor people and there is not really a special trick. I just kind of pair program, and when we start I drive and eventually they drive and then once that's comfortable I leave them alone and leave them to ask me questions. I've found this mostly effective.
Explaining things to junior developers isn't so different from explaining things to anyone else. In the course of your job you probably have to explain concepts to your co-workers and to non-technical people, right? A junior is somewhere between those and you can calibrate as you go.
- kenhwang 9y ago> In the course of your job you probably have to explain concepts to your co-workers and to non-technical people, right? I love how this is becoming the norm for engineers. I still run into engineers that seem to just code by themselves in a cave all day and the only human they communicate with is their (often non-technical) manager once every other month. Communication is one of those skills that feels effortless if you're used to it, and like an nonstop anxiety attack if you're not.