He was not a formally educated man. But he saw something in me that I could not yet see in myself — and he was willing to bet everything he had on it. That is the most important thing anyone has ever done for me.
The Town Where Dreams Felt Distant
I grew up in a small, close-knit community where everyone knew everyone. Opportunities were limited, and ambition — real ambition, the kind that required leaving — was not something the environment encouraged. Most paths led somewhere predictable. My father had no blueprint for what he was about to do.
When I completed my 12th standard, he made a decision that the family could barely afford: he would send me to Lahore. Six hundred kilometres away. A city of millions. A hostel. A world that bore no resemblance to the one I had grown up in.
My grades until that point were, in my own honest words, okay-ish. Not a guarantee of anything. In our society, academic excellence is often treated as the only admissible evidence of a future worth investing in. My father had different evidence. He had something harder to quantify — a belief in my capacity that preceded any proof of it.
He believed in me, even when it meant taking risks we could barely afford.
Lahore, and the Lessons No Classroom Teaches
Stepping into Lahore as a hostelite was overwhelming in ways I had not anticipated. The scale, the noise, the anonymity. As the eldest son, the weight of my father's expectations sat alongside my own uncertainty. He wanted a respectable job for me. That felt both close and impossibly far away.
The small things revealed the distance most sharply. The mess food — which should have been one of the better parts of a student's day — was nothing like the meals my mother cooked. That is when I first understood what it costs someone to feed you well every day without ever being thanked for it.
My bachelor's degree was a struggle. I did not enjoy much of it. I was uncertain where my real strengths were, or whether I had any that would matter in a city this size. Then a friend changed the trajectory with a single suggestion: take the admission test for a Master's programme in Computer Science.
The test was rigorous — analytical reasoning, problem-solving, logical thinking. The kind of thinking I had never been formally trained for. I sat it, and I surprised myself. I passed.
The Postman Who Knew Before My Father Did
In my first semester of the Master's programme, I secured a 3.85 GPA. Dean's Merit List. Full scholarship for the entire tenure.
I went home during the break. The result had arrived by post — an envelope that contained not only my grades, but an appreciation letter and the scholarship confirmation. I had asked the local postman to hand it directly to my father.
The postman looked at me with an expression I still remember. "Should I hand it to your father — or should I not?" He already sensed that something in that envelope was worth delivering with care.
He handed it over. The look on my father's face is not something I can translate into prose. Six hundred kilometres of distance. Years of uncertainty. One envelope. It was the first moment I felt I had given something back.
Before Google Maps, There Was an Idea
In the final semester of my Master's, two friends and I needed to choose a project that would stand out. Our advisor, testing us, suggested something that made us laugh at the time: build an online version of Excel, PowerPoint, and Word. This was early 2002. Microsoft Office was untouchable. The idea seemed absurd.
We declined — and chose something we considered more ambitious. An Intelligent Trip Planner with AI-driven itinerary generation. Users would provide budget, dates, and travel preferences. The system would think. It would plan. It would produce a complete trip, intelligently optimised.
This was 2002. Google Maps would not launch for another three years. AI-powered consumer applications existed mostly in research papers. We were undergraduate engineers in Lahore building something that the industry would not reach at scale for over a decade.
We poured ourselves into it. The SRS was thorough. The architecture was sound. The vision was genuinely ahead of its time. But when it came to the feature that defined the whole project — the intelligence, the AI — we ran into a wall. The learning curve was steeper than we had estimated. The algorithms did not cooperate. The semester had a deadline that the technology did not care about.
The examiner was direct: in its current state, this project is a failure. We asked for an extension. It was not granted. We removed the AI component — the entire reason the project existed — and submitted what remained. What could have been an A+ became a B.
The irony I carry with me now: we laughed at our advisor's idea of an online Office suite. Google Docs proved us wrong within a few years. Our own idea was correct — the timing was simply before we had the tools to execute it. We were not fools. We were just early.
The Advice That Has Outlasted Everything Else
That night, after submitting the stripped-down project, I called my father. I told him what had happened — the failure, the missing feature, the grade, the disappointment. I was not looking for comfort. I think I was looking for permission to be honest about how badly it had gone.
He gave me something more permanent than comfort. He gave me a principle:
Speak the truth with your examiner, even if it means failing the project. Never lie about a functionality that doesn't exist.
That sentence has followed me through every job, every system I have built, every incident I have faced, every demo I have given, every technical review I have sat in. The instinct to over-promise — to present a system as more complete than it is, to smooth over the gap between the vision and the reality — is one of the most persistent pressures in our industry. My father named it when I was twenty-three, with no knowledge of software architecture, and he was completely right.
Now I Am the Father
I have three sons — fifteen, thirteen, and eleven. They will face their own equivalent of Lahore: the overwhelming city, the mess food, the uncertain grades, the project that does not go as planned. I watch them now and I see myself in the early pages of a story I already know part of.
I sometimes falter when faced with their small failures. I feel the pressure to push, to correct, to want more for them faster than is fair to ask. And then I think of my father, who had every reason to doubt and chose instead to believe. Whose bet on me was not contingent on my grades being perfect or my projects succeeding.
Success Is Not What I Initially Thought It Was
Not the scholarship. Not the Dean's List. Not the career built on top of those credentials. What I carry forward — and what I try to pass on — is simpler and harder: be humble when you succeed, honest when you fail, consistent when it is inconvenient, and willing to grow when the evidence says you are wrong. My father modelled all four without ever using those words.
The Intelligent Trip Planner earned a B grade. Twenty-three years later, the world is full of exactly what we were trying to build. I do not look back at that project with regret. I look back at it with a kind of gratitude — because the failure produced the most useful advice I have ever received, delivered by the person who had the least formal reason to know it.