Jokes apart, the reuse that is drummed into an IT student is usually in the context of OOP, or programming where we talk of reusing the code written once to be used elsewhere. The term reuse, though, goes much further. We reuse a great many things without even realizing it. For instance, software development contracts will often have similar, even almost identical clauses. The reason is that similar problems are expected to arise, and therefore are dealt with in a similar manner. Whilst these rudimentary applications of reuse are valuable, reuse itself can be far more valuable by way of mentoring (something that only came to mind after I read this)
The reason I choose to link mentoring to the concept of reuse is because mentoring provides an apprentice with the opportunity to capitalize upon the experience of the mentor. Organizations such as IBM, Microsoft, InfoSys have mentor programmes to help their employees growth.
What should I look for in a mentor?
The thoughts that come to my mind are -
- Trust & Communication (the two must go together)
- Better than average understanding of the domain (Finance, Software...) under which the mentoring occurs
- Better than average Time Management skills, and as a corollary - not a workaholic
- Compatibility
- It simply doesn't make sense to assign someone as a mentor, only to find they're not able to justice to either their primary role or their mentor role.
- The apprentice might pick up the bad-skills too
- Poor time-management might also mean a stressed work-style; in the long run this could be detrimental to health, and to teamwork.
