Most people think a CGPA calculator is only about formulas.
I thought same.
Then I started building one.
Very quickly I realized students do not struggle with calculations. They struggle with everything around them.
Finding subject credits.
Checking semester details.
Making sure nothing is missed.
Entering same information again and again.
That is where most of time goes.
So I changed my approach.
Instead of building another calculator, I focused on removing unnecessary work.
I wanted students to spend a few seconds selecting their grades instead of several minutes searching through documents.
That meant organizing academic data first.
Not writing code.
I spent days reading official SRM curriculum documents and arranging subjects and credits into a format calculator could understand.
It was repetitive work.
Sometimes frustrating.
But I knew every hour spent behind scenes would save students time later.
One lesson stood out.
A good tool is not one with most features.
It is one that asks users to do less.
Today calculator automatically handles subjects and credits based on selected course and semester. Students only choose their grades and calculator does rest.
If you are curious to see how that idea turned into working tool, you can explore it here:
CGPA Calculator for SRM University
It also includes separate tools for GPA, CGPA and arrear calculations, all designed with same goal of reducing manual work instead of adding more steps.
Building this project changed how I think about software.
Sometimes biggest improvement is not adding another feature.
It is removing one unnecessary click.
Have you ever built something that looked simple on outside but took far more work behind scenes? I'd love to hear your experience.
Top comments (0)