Ah… reacalling my mentoring sessions at ADOT (Advanced Dimploma in Object Technolog) in 2001 at seed Infotech, Pune. I could see each one is doing fantastic in their career. Most of them are CEOs, CTOs, Solution Architects, Senior Vice Presidents, Solution Providrs etc. Most of them are in India as well abroad enjoying their work life balance. So happy to see them in this frame; when we were having small trip at Sinhagad for at Pune. Could you figure out me in middle? This was the joyful expereince after going through learning experiences after six months of learning process. But when I recall the time; when they were sturggling in their studies before six months. I was at receipting mode, listening mode and in mentoring mode and accepting their frustration in learning new things, tryouts. Being a mentor is, a every day new learning expereince. It is still going on today. Now it is in Transflower. Transflower is learning through reflections, introspection and responding.

I remember my first batch of students. Fresh out of college, eager to “get a job fast,” but not quite ready for the real challenges of software development. This is something I’ve witnessed countless times over the years. Graduates often have the academic knowledge, but when it comes to real-world application, there’s a gap. Let me share my observations and experiences. These helps me reorganizing, restructuring learning and mentoring strategies at Transflower. Learning and Teaching is my passion. Sharing is caring.

1️⃣ The Problem I Often See

Passive Learning Mindset
I’ve had students who, during mentoring sessions, would sit quietly, nodding along, and wait for me to tell them exactly what to do. In college, they were trained to watch and listen, complete assignments, and pass exams. The idea of exploring, experimenting, and building something themselves was new—and frankly, uncomfortable.

Resistance to Hands-On Learning
The first time I asked a student to build a small CRUD application from scratch, I saw hesitation. They would say, “Can’t we just watch a video first?” or “Can you give me the code template?” Real projects demand problem-solving, debugging, and critical thinking, and many resist because it’s harder than listening or copying.

Frustration with Slow Progress
I remember one student trying to integrate a simple REST API for the first time. After an hour of errors, they wanted to give up. They expected to become “job-ready” overnight. But software development isn’t magic—you learn by struggling, failing, and trying again.

Lack of Reading and Self-Learning Habits
Another common observation: students shy away from documentation, tutorials, and API references. They’d rather wait for me to explain. I had to teach them to read, interpret, and experiment with documentation themselves—a skill crucial for survival in the software world.

2️⃣ Why This Happens?

From experience, I’ve noticed these patterns repeatedly:

• Colleges focus heavily on theoretical knowledge, exams, and assignments, rather than hands-on projects.
• Students become habituated to memorizing and completing tasks, instead of solving real problems.
• The job market often promises “immediate placement,” which encourages shortcuts and superficial learning.

3️⃣ How I Approach Mentoring This Gap

Over the years, I’ve developed strategies that slowly reshape students’ mindset and skills. Happy to see lot of benifitted and become self explorers:

1. Set Expectations Early
I always start by explaining: “Watching alone won’t make you employable. Real skill comes from doing, failing, and reflecting.” Sharing my own early struggles in coding and projects helps them see that failure is part of learning.

2. Project-Based Learning
I break down projects into small, achievable tasks. Even when students struggle with the first tiny feature, completing it gives them confidence. Gradually, they can handle larger features and modules.

3. Encourage Self-Learning Habits
I assign short reading exercises—API documentation, tutorials, or even problem-solving blogs. I ask them to write what they understood in their own words. This habit alone transforms a passive learner into an independent thinker.

4. Simulate Real Work Environment
I introduce code reviews, debugging exercises, Git workflows, and team collaboration, mimicking a real software project. Initially, they resist the discomfort, but soon they understand that real development is messy and iterative, not linear or perfect.

5. Address Frustration
Whenever I see frustration, I share stories from my early career—how I debugged for hours, failed multiple times, and finally succeeded. I emphasize resilience, patience, and problem-solving mindset. Over time, students begin to embrace challenges rather than fear them.

6. Gradual Autonomy
I reduce hand-holding gradually. First, I guide them step by step; later, I step back and let them search, experiment, and implement solutions independently. The transformation is remarkable—students who once depended on me now take ownership of their learning.

4️⃣ Key Insight

The truth I’ve learned as a mentor: the core challenge is mindset, not capability.

• Most graduates can learn and excel, but they need guidance, structure, and patience.
• Mentoring is as much about shaping their learning habits and mindset as it is about teaching technical skills.

Love to be a co-learner in your learning journey. Tap your potential.

Mentor as as Service from 1997

Transflower.