3 ms·
This is also why it's useful to hire new people once in a while and pay attention to what they think. A new, junior hire will note many of the same things as an
by meuk 7y ago
This is also why it's useful to hire new people once in a while and pay attention to what they think. A new, junior hire will note many of the same things as an expensive consultany. With the difference that people actually listen to the observations of the consultant , while they expect the junior dev to get used to things.
- thinkingkong 7y agoAgreed. A helpful exercise is to ask them to keep a log for the first 30 days. Ive always found incredibly useful information in there.
- iforgotpassword 7y ago+9000 I'm "using" our interns for this. First task is to create a document where they're supposed to write down everything that seems odd, overly complicated or broken. Even though they're sometimes in their third semester only, this pretty much always brings up something that can be improved on the spot without refactoring a dozen components. But also for all the things that were actually just a case of the intern being inexperienced or too naive it's great for them to go back to this document after three months and see how their understanding changed over time.
- ssivark 7y ago> But also for all the things that were actually just a case of the intern being inexperienced or too naive it's great for them to go back to this document after three months and see how their understanding changed over time. Seems like a fantastic exercise, with benefits both ways. In hindsight, this seems so simple and powerful that I wonder whether it's a commonly accepted onboarding exercise for new team members, especially junior ones. If not, it probably should become.