Thinking about starting a mentorship with a young programmer. Any weigh in about things to do / not do?
All of the DOs are based on what my mentor did when I was 16, the DON'Ts are just my own opinion: DO: Try to answer the questions they have. DO: Identify sub-fields of interest, and encourage learning of them. DO: Teach the difference between well-written and badly-written code.
-
-
DO: Teach the value of testing as soon as possible. Older me would slap the piss out of younger me for younger me's disrespect of QA. DO: Try to teach them to be a well-rounded coder. DON'T: Put *too* much emphasis on knowing everything, however.
-
DON'T: Make them feel bad for not knowing something that might be obvious given your many years of experience.
Keskustelun loppu
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.