Career
I Scored 3 Marks in Math. The Method That Got Me to a 9.6 CGPA.
I went from 3 marks in math to a 9.6 CGPA as a computer engineer. What changed was the yardstick I measured myself against.
learning methodhow to learn new skills9.6 CGPA
I once scored 3 marks in math. For a long time I treated that number as a verdict on me, and everything I did afterwards was shaped by it. I ended up a computer engineer with a 9.6 CGPA, and when people ask how, they expect a story about working harder. That is not what happened. I changed the thing I measured myself against, and then I kept using that loop for everything.
I never wrote the method down as a system, so this is my reconstruction of it, years later. I think the reconstruction is accurate, but treat the details as how I remember it.
Why was I so bad at math in the first place?
My honest answer is that I was lost, and I was comparing. The numbers on the blackboard looked like noise to me, and the formulas felt like a wall I would never get over. Each time I got a result back, I put it next to my classmates’ results and read the gap as my ability.
That comparison did real damage. It made every bad mark feel final. When you believe a gap is fixed, you stop trying to close it, and I think that is what actually kept the score where it was.
What do you measure when you stop comparing?
Your own previous version. That is the entire switch.
You would not compare one product’s KPI growth against a different product’s. The two have different starting points, different users, different constraints. Nobody learns anything from that chart. Yet we do it to ourselves constantly, with people whose starting point we know nothing about.
So I started tracking my own progress on three clocks: week over week, month over month, and year over year. The weekly view tells you whether your current habit works, and the monthly one shows whether a topic is sinking in. The yearly view took a while to matter, but it was the one that finally showed me a line going up.
The small wins mattered more than I expected. I celebrated them on purpose, because a method you cannot feel working does not survive the first bad week.
How do you sort what is worth worrying about?
Some of what goes wrong is in your control and some is not. Wasting energy on the second kind is the cheapest way to lose a month.
My rule was simple. If I could control a situation, I took action and looked for a fix. If I could not, I accepted it and moved on. A paper that already got marked is the second kind. The next paper is the first kind. Most of my worry used to be pointed at the marked paper.
What does “try, fail, repeat” look like in practice?
Failure is going to happen either way, so the useful question is what you do in the hour after it.
When something went wrong, I did not stay in it. I looked at what specifically went wrong, took the lesson, and tried again with a clearer idea of what to change. The review step is the part people skip. Repeating without reviewing is just failing more times.
A rough version of the loop:
- Attempt the thing.
- Find the exact point where it broke.
- Fix that point and attempt again.
Does your environment really change how you learn?
I think it does, and I would put it higher than most study advice does. I kept asking questions, and I was lucky to have friends who liked learning as much as I did. Curiosity was normal in that group, so asking a basic question cost nothing.
If your environment makes you feel stupid for asking, that is a real cost on your learning speed. My advice is to find the people where the question is welcome. If you cannot change the room, try to be the person who makes it safe to ask.
Does the method work outside math?
I think so, because nothing in the loop is specific to math. Here is how it looks if you point it at anything unfamiliar.
Start by writing down where you are today, not where the expert is. Aim for one small win quickly, because it tells you the method is working. When something breaks, find the exact step, fix it and go again. When you are stuck on something outside your control, accept it and route around it. And ask questions early, even the basic ones.
I have started over several times in my life, in different cities and in different countries, and I suspect the loop is part of why each restart felt survivable. The loop depends on honest measurement against yourself.
Today I mentor aspiring product managers as a senior PM, and what I tell them follows from all of this. Your timeline is not the same as anyone else’s, so a leaderboard has very little to say about it.
I do not know how much of my 9.6 was the method and how much was just that I finally stopped flinching. My guess is that the two are the same thing. Someone afraid of the number rarely experiments, and measuring against yourself takes that fear out of it.
A checklist to try this week
- Pick one skill you are bad at and write down your honest level today.
- Choose a clock, weekly or monthly, and check against your own last result.
- List the things around it that you cannot control and stop spending time on them.
- After every failed attempt, write one line on the exact step that broke.
- Find one person you can ask a basic question without feeling judged.