Thing approves.
I notice things.
Then I can't leave them alone.
A tool for engineers preparing for coding interviews.
It maps which algorithmic patterns you've actually practiced, shows what you're missing, and tells you what to solve next.
I was solving problems every day and still didn't know what to solve next, or which patterns I was completely avoiding.
Most people grind hundreds of questions without knowing where their gaps are. GrindLens maps your submissions against problem patterns, shows your weak spots, and gives you a clear next problem to work on.
Each of these started because I wanted to see how something worked, or because doing it manually was annoying.
The first version was just a Python script fetching my LeetCode submissions, a MySQL database, a small PHP API, and a JavaScript dashboard to track streaks and weak topics. That script ran for months before I decided to turn it into a real product.
So I built a chat app with no database.
There are no accounts or message logs. Messages only exist in memory while the room is open, and disappear completely as soon as the session ends.
The original reason was considerably less technical.
I got tired of doing it. So I made a bot do it.
A bot that cronjob.org triggers on schedule, checks the LeetCode GraphQL endpoint for accepted submissions, and posts them directly to our Discord server. I set it up once, and haven't had to touch it since.
Most of the work wasn't writing code. It was reading through unfamiliar architecture, following existing conventions, and making sure my changes didn't break things downstream.
Worked inside Rocket.Chat's message-parser package in TypeScript. Fixed timestamp parsing inside formatted markdown, added defensive guard tests for isNodeOfType, and resolved regression edge cases in emoji handling within reducePlainTexts. Consolidated by maintainer ggazzo into batch merge PR #39853.
Selected contributor for Nexus Spring of Code (NSoC 2026). Merged 30+ Pull Requests across JavaScript and TypeScript open source repositories, ranked 70th out of 988 contributors nationwide.
I solve problems every day under strict time and memory limits. It started as interview prep, but after a 200+ day streak it's just part of my daily routine.
I started sharing updates while building GrindLens: what broke, what worked, and what I was learning along the way.
47 posts across three months.
Some GrindLens.
Some DSA.
A lot of things that had nothing to do with either.
I started posting anyway.
Short updates, small experiments, and talking to other developers who are building things.
Follow on X →“I don't like knowing better and doing nothing.”
I skipped the gym sometimes, but I still worked out at home. Showing up every day doesn't feel like discipline anymore, it just feels weird to stop. Most of it is just keeping distractions out of the way.
I spent years writing things I'd never let anyone read.
I'd tear it up. Small enough that nobody could piece them back together.
I don't do that anymore.
He stopped talking.
Words are wasted on people who only hear themselves.He stopped looking.
There was nothing out there worth the damage to his eyes.The dark suited him.
It was the bright ones that lie.They called him broken.
He did not care.
He did not come back.
What came back was something else wearing his patience as a coat.Not a villain.
Villains still feel the need to explain themselves.Not a hero.
He has no interest in saving people who walked into the fire themselves.I'm still figuring out what all of this becomes. For now, I'm building.
Computer science student based in India. Currently building GrindLens and working on backend systems. If you want to talk about something interesting or need help building, reach out.
people have been here.