What your mentor does not tell you?!

Abhishek Jain
2 min readOct 14, 2020

--

Is my mentor not telling me something?

You might be in a position when you feel that your mentor is hiding something. He/she might be talking usually but deep inside you feel a crunch which you are not able to resolve.

As a developer mentor, they assume and expect certain level of understanding from you. Even if you’re a fresher or with internship experience, you’ll be considered to have at least working knowledge of the tech you’re working on.

What is expected of me?

Mentor are guides not teachers. Students or early professionals do not understand the difference between a mentor and a teacher.

A teacher will make you understand what’s the difference between an array and an object.

A mentor will guide you when to use an array and when you can use an object.

What should I ask my mentor?

The logic and basic data structures is expected to be known if you’re a fresh engineering graduate. But how to use that logic in real-time applications with the best practices are what mentors are for.

Some young individuals fail to understand this minute difference and in turn waste the effort and energy given by the mentor, which brings me to the question at hand. What does my mentor does not tell me?

The answer

Mentor seeks for the level of comfort on which you can work with him/her. If that is not achieved, the mentor will be forced to work with you. The mentor thinks of you to ask intriguing questions, for which the answer itself is hard for mentor to resolve. It’s a heck of a task to make someone understand a working application and to train for him to get to the same working knowledge. Instead of asking of the better way to write a logic(on which mentor does not give a second thought), it’s better to ask the best practices to write that logic(which you should be able to figure out on your own, you have internet and google, go-fish).

How to know which questions to ask?

That’s a good thought too. But the answer is also pretty achievable.

You ought to ask question which does not include answer to help write a logic.

Ask a question which makes you understand more about the task rather than the code. Ask more Why questions rather than What questions.

Do comment, if you implemented it or found it useful! Thanks.

--

--

No responses yet