ClassCom.
Built for my world. Shared with yours.
Hey, I'm Shan Kumar.
I built ClassCom out of sheer spite because the official college portal runs at the blistering speed of 1998 dial-up internet and crashes the exact microsecond results drop.
I essentially spent 200 hours coding a whole platform just to save 45 seconds of daily effort. Peak engineering efficiency.
Instead of studying or touching grass, I reverse-engineered timetables, wrote autonomous grade scrapers, and automated lab PDF prints so I'd never have to hold an infected xerox pen drive ever again.
I wasn't the only unhinged one though — shoutout to my fellow co-conspirators in Team CodeCommit: Dheeraj Pusuluri, Jessani Radhika, Kavali Shashank (they stopped me from rewriting the whole database at 3 AM).
Age:Probably an old dude
Role:Chief Bug Generator
Campus:CMRCET (Surviving, barely)
Stream:CSE (Data Science) • 100 tabs open
Specialty:Turning 1 bug into 27 bugs
Started as a little experiment.
I wanted a space that worked the way I wanted it to. So I started building one.
No grand master plan. Just an idea, a little curiosity, and a lot of figuring things out along the way.
Okay, so what can it do?
Here's what I've been building into ClassCom.
Autonomous Results & SGPA Radar
When the college server crashes on result day, ClassCom parses your grade card in seconds.
Every semester release, the autonomous results portal crawled to a complete halt. I wrote a scraping engine that talks directly to the college backend proxy, extracts student grade records, calculates SGPA & CGPA trends, and computes section ranks automatically.
Anyway, that's ClassCom.
A little project of mine, built with curiosity.
Feel free to explore.