Mentoring Young Developers in the UAE

The Student Who Taught Me

The student walked into my office hours, sat down, and said: Professor, I do not understand recursion. I had heard this sentence dozens of times. I reached for my standard explanation — the factorial function, the base case, the leap of faith — and she stopped me. No, she said. I understand the definition. I do not understand why anyone would choose to think that way. It was the best question I had ever been asked about recursion, and it reframed my entire approach to teaching.

Mentoring, I have come to believe, is not the transfer of knowledge from a fuller container to an emptier one. It is the art of helping someone discover that they already hold the question, and that the answer lives in the same place. The student who asked why was not struggling with recursion; she was struggling with trust — trust that a solution that calls itself could ever terminate, trust that the mental model was not a trick. Once she trusted the model, the code wrote itself.

What Actually Helps People Grow

After years of mentoring students and junior engineers, I have noticed that the interventions that matter are rarely the ones that feel productive in the moment. The code review that takes thirty minutes because you explain why, not just what. The conversation where you admit you do not know the answer either. The assignment that is slightly too hard, paired with the assurance that being stuck is the point.

• Give specific, actionable feedback — not good job or this needs work, but this variable name misleads the reader about the intent, try this.
• Expose your own learning — let mentees see you debug, struggle, look things up. Expertise that looks effortless is intimidating; expertise that looks earned is inspiring.
• Ask questions you do not know the answer to — the mentee who researches alongside you learns research, not just facts.
• Praise the process, not the person — you worked hard on this teaches growth; you are smart teaches fragility.
• Make introductions — the network you open for a mentee may matter more than any technical skill you teach.

The Patience Problem

The hardest part of mentoring, for me, has been calibrating patience. Lean too far one way and you solve problems for the mentee, which feels helpful but teaches dependency. Lean too far the other way and you leave them stranded, which feels rigorous but teaches despair. The balance is not a formula; it is a feel, developed through repetition and honest reflection on which interventions actually led to growth and which felt good but accomplished little.

I have learned to watch for a specific signal: the moment when the mentee is about to give up but has not yet. That is the moment to intervene — not with the answer, but with a question that reopens the door they were about to close. The intervention is small. Its effects compound. The engineer who learns to find their own doors becomes a mentor themselves, and the practice propagates in ways you will never fully see.

The mentor does not create the engineer. The mentor creates the conditions under which the engineer creates themselves. The difference matters because the first model is arrogant and the second is humble, and humility is the only stance from which mentoring actually works.

The Reciprocity I Did Not Expect

I expected mentoring to cost me time. I did not expect it to make me better. But the discipline of explaining things clearly to someone who does not share my assumptions has sharpened my own thinking more than any advanced course or conference. The student who asks the naive question reveals the assumption I forgot I was making. The junior engineer who proposes a solution I would have rejected makes me articulate why, and sometimes I cannot, and the rejection was wrong.

Mentoring in the UAE has a particular texture because the students come from backgrounds I did not share — different educational systems, different languages of instruction, different expectations about the relationship between student and teacher. The cultural humility required has been its own education. I came to teach and found myself learning, which is, I have come to suspect, the only honest way to teach. The engineers I have mentored are not my legacy; they are my teachers, and the debt runs in the direction I did not anticipate.