---
title: "I Don't Think About Motivation"
description: "People DM me every day asking how to stay motivated and where my ideas come from. This is the long answer, with the bad CGPA, the OA rejections and the two hour builds."
date: 2026-11-20
tags:
  - life
  - building
  - open-source
  - guide
---

> okay this one's long. it's basically my reply to every "bhai motivation kaise laate ho" DM i've ever gotten, written down once so i can just send the link from now on. read it in parts if you want, i won't mind.

On the day my fourth semester results came out, my CGPA went down again.

I was talking to a friend about it and said, half joking, "vo to open source se hi job lagwa lunga." I'll just get a job through open source. Before she could even reply I added, "achhe lagne ke liye bol raha hoon bas." I'm only saying it so it sounds good.

I didn't believe a word of it. I was near the bottom of my batch, under the placement cutoff, and that line was just something you say so the conversation doesn't get depressing. The note I left in my journal that day was more honest: "cgpa is done, 7.21 (cant sit in intern now :) ) gotta figure out something. but dont know what".

<mark>A few months later, a small version of it actually happened.</mark>

I'm not writing this from some finish line. I'm 19, still in college, still figuring most of it out, and what I have is a checkpoint, not a success story. But a lot of people ask how I got even this far, and the honest answer is that I didn't wake up motivated one day and turn my life around. That isn't what happened. What happened was a lot more boring than that, and the good news is that boring things are easy to copy.

---

## The DMs

Almost every day somebody sends me a version of the same message. How do you stay motivated? How do you keep building every day? Where do you even get so many ideas from?

I give the same answer every time, and I can tell it lets people down a bit, because they were hoping for a routine or some trick. The answer is that <span class="key">I don't think about motivation at all.</span> I don't check whether I feel like building before I start, and I don't wait around for the feeling to show up.

What keeps me going is curiosity, and showing up on the days the curiosity is quiet. In one line that sounds like nothing, so the rest of this post is the long version, with the real stories and numbers and also the parts that went badly.

---

## Where I started

I'm at IIT Jodhpur, CSE, 2024 batch. My rank is <span class="bad">somewhere around 90 out of 120</span>, and my CGPA is about 7.2. Most companies that come to campus here want 7.5, so I couldn't even sit for most of them.

I did try the normal route first. In first year I did DSA in C++, solved 450-something problems on LeetCode and got to about 1429 on Codeforces. It taught me how to think and I don't regret any of it. It just never pulled at me the way a half broken project did at 2am. During midsems in third semester I posted this at 2:20 in the morning: "I'm writing notes for tomorrow's exam, I'm really missing coding now." That was pretty much every exam season for me.

I also tried the motivation route properly, and I have receipts, because since July 2025 I've kept a public journal thread in a Discord server called Study Together. I named it "Grinding hard until I can buy Porsche 911 Carrera Cabriolet", which tells you everything about where my head was. The first message says "From today on, ill share everything im going through and everything im doing.. I need to grind hard and get a amazing life. :)"

Those first few months are mostly caps lock. "LETS GRIND!!!!!!" "new day, new grind begins!" Every to-do list that summer had "Can't Hurt Me, audiobook (1 hour)" on it, and I don't think I ticked it once. In October I started a "Winter Arc" with a list of "arc laws" at the bottom of every entry, and one of them was literally "Discipline beats motivation every time." A week into the arc, I wrote "probably will stop writing on here~".

I tried the grind version of consistency on X too. Last December I was posting day by day logs there. "Day 2, 14 hours in." "day 11, 16 hours in, locked in completely (ig)." And in between those, "Day 7, 6-7 hours in: wasted a lot of time." I couldn't keep it up. By June I was replying to someone, "I start a lot of things but never stay consistent.. gotta fix that." So when I talk about consistency later in this post, please don't picture 16 hour days. I tried those and they fell apart within a few weeks.

Then internship season started. In July <span class="bad">I didn't get shortlisted for Google's on-campus SWE internship</span>. The night before the Goldman Sachs OA, I posted that I didn't have any chance because of my CGPA but I'd give it my best anyway, and the next day I missed a `1e9` constraint in one of the questions. After that it was one OA after another: Flipkart GRiD, BNY, Adobe, Roblox, Groww, Microsoft. Most of them went nowhere. <span class="muted">A later one rejected me for writing my solution in C++ instead of Python, which still annoys me.</span>

---

## The start of fifth semester

The lowest point was the start of fifth semester, because that's when internships land for everyone else.

Some people in my batch had one sorted before the semester even began, before we were back on campus. They could relax for all of third year. A few were fairly sure of a pre-placement offer, which basically means two years of nothing to worry about.

I had nothing. The day I left home for college in July, I wrote in my journal, "gotta grind these 1-2 months until i land a internship then i can chill!" Two weeks later it was "cant just let motivation hits take me anywhere." I was still doing DSA, still giving OAs, and nothing was landing.

On August 11, at 1:26 in the morning, I wrote this. I'm copying it exactly, typos and all:

> i am not being stuck with this shi\*\*y life style  
> its enough being in a bad place like this  
> do i really deserve this as my end goal?  
> no i dont.  
> i thought and dreamt of something completely different.  
> i know its hard.  
> and i've been chasing cheap things  
> cheap dopamine.  
> and getting stuck in the loop.  
> being motivated, for a bit.  
> getting to the same place after a while.

<mark>"being motivated, for a bit. getting to the same place after a while."</mark> That's the most accurate description of motivation I've ever read, and I wrote it half asleep without meaning to.

Eleven days later, Microsoft didn't shortlist me. The journal entry is three lines: "didnt get shortlisted in microsoft", "cgpa regret lmao", and then "no one stopping me to getting an intern at a startup."

That was the fuck it moment. I'm not angry at anyone in my batch, they worked for what they got. Five days later three of my friends got Microsoft internships and I wrote "SO HAPPY FOR EM!!", and I meant it. But I'd stopped waiting for the normal path to pick me. <span class="key">Nobody was going to hand me an internship, so I was going to go and get one myself.</span>

There was no music playing and no big speech. The very next day's journal entry says "i was studying system design and cooking break-scale." I went back to the one thing I was actually good at, which was building something nobody had asked for. On August 26 I replied to someone on X, "Cgpa ni hai isliye fati hai 🫠" (no CGPA, so I'm scared), because I was still scared. Two days after that, I wrote "finally set-up, with good first issues :) ready to be public :)" and put Breakscale online.

---

## Where things are right now

I kept building whatever annoyed me, and whatever I didn't understand, and I put nearly all of it on the internet. This is the checkpoint as of writing, mostly so you know the stories below are real:

- <span class="good">A DevRel job at a YC startup that I never applied for.</span> It started with a DM from someone who'd been using one of my projects.
- [Google Summer of Code 2026 with KDE](/blogs/gsoc-selection), on Kdenlive, which I got into the same month as that results day and finished in September.
- [Breakscale](https://breakscale.tech), a system design simulator that people I've never met now send PRs to.
- [hatchzip](https://github.com/xevrion/hatchzip), which <span class="key">a lot more people use than I ever expected</span>. A month ago it was a conversation at a party.
- [gyotaku](https://gyotaku.app), plus a long tail of small tools a handful of people use every day.

<div class="callout good">

My first post on X, in September last year, was "well, well, well, i'm now on X, will start shit posting on here too :)". It got 163 views. I had a bad CGPA and a few repos nobody had starred. I didn't have some special motivation that the people in my DMs are missing. I had a lot of curiosity and I kept not stopping, and you can start doing both of those tonight. And none of this means I've made it. It's a checkpoint, and most of what I want to do is still ahead of me.

</div>

---

## Why I stopped waiting to feel like it

You probably know how chasing motivation goes. You watch a productivity video at 11pm and feel ready to fix your whole life. You make a Notion template and plan a perfect schedule that starts Monday. Then Monday comes, the work gets boring twenty minutes in, the feeling's gone, and you go and find another video. Meanwhile you start to think something's wrong with you.

Nothing's wrong with you. <mark>Motivation is a feeling, and feelings come and go.</mark> If your building runs on that feeling, it stops the day the feeling does.

So I ask myself two other questions. The first is whether I'm curious about the thing. Curiosity doesn't need hype. It's a question stuck in your head that won't leave until it gets answered, and you don't need to pump yourself up to go answer it.

There's some real science behind this too. A 2014 study in *Neuron* by [Gruber, Gelman and Ranganath](https://pmc.ncbi.nlm.nih.gov/articles/PMC4252494/) found that when people were curious about a trivia question, the dopamine-related reward circuit in their brain got more active, and they remembered the answer better. They even remembered unrelated faces shown to them while they were curious better. So curiosity <span class="key">actually makes you learn better</span>, on top of feeling nicer than forcing yourself.

The second question is whether I showed up today. A well known [habit study from UCL by Lally and colleagues](https://www.ucl.ac.uk/news/2009/aug/how-long-does-it-take-form-habit) found it took people 66 days on average for a daily behaviour to become automatic, with a huge range, from 18 days to an estimated 254. So you won't feel like a builder after one weekend, and that's normal. If you keep at it, opening the laptop stops being a decision at some point. You just do it, like brushing your teeth.

---

## Curiosity: build it until you get it

A lot of my projects start with "wait, how does this actually work?" and only later turn into something useful.

My [peer-to-peer chat app in Go](/blogs/peer-to-peer-chat-app-go) started like that. Nobody needed it. My brain just wouldn't shut up until I understood how two computers talk without a server sitting in the middle.

Breakscale is the best example I have. I was learning about load balancers for system design, and I'd just fumbled a system design question in an interview, which was still bugging me. Every article said the same things: add a cache, add a load balancer, add a queue. None of them showed what actually happens when the system breaks, and I didn't want to read another one. I wanted to *see* one fall over.

I went looking for a simulator and everything I found was half built, or fake animations that only looked right. So I built my own over a weekend. You put a system on a canvas, drag the traffic up and watch it collapse, and every number on screen comes from a real discrete-event simulation. In the retry storm example, failures jump from 0% to 93% after a tiny bump in traffic, and you can drag the slider back and forth across that cliff.

On the Thursday it had <span class="key">8 stars</span>. I posted it. That weekend thousands of people came to break things on purpose, and <span class="good">strangers started sending PRs that fixed bugs in my simulation logic</span>. Ten days after the repo went up, a DM landed in my inbox, and that DM turned into the job I have now.

I wasn't building it for a job. I'd been confused about load balancers for weeks and I wanted to stop being confused.

That feeling is still the main thing I run on. Two weeks ago I started learning assembly, and two days in I posted "just cracked a program by deleting one instruction 😭 this is so fun wtf." I told someone this about a game recently, and I think it applies to everything: <span class="muted">"dont read any guides, there is no tutorial, curiosity always rewards you!"</span>

And people have worked this way for a long time. In 1991 a student in Helsinki posted on a newsgroup that he was writing a free operating system, ["just a hobby, won't be big and professional like gnu"](https://lore.kernel.org/lkml/30th.anniversary.repost@klaava.Helsinki.FI/). That was Linus Torvalds, and the hobby became Linux. Years later he called his autobiography *Just for Fun*.

---

## Where the ideas come from

When someone asked me this on X, my reply was "I dont sit and think of ideas I just make whatever i face in real life." That's still the most accurate version.

Someone else once asked me, kind of suspiciously, if I get my ideas from AI. I don't. An AI is trained on things that already exist, so if you sit brainstorming with it for hours you mostly get remixes of products that are already out there.

What I do is <mark>write down small problems from my own life and then leave them alone for a while.</mark> I keep an Obsidian vault I call brain, and when something annoys me, even something tiny, it goes in as one line. I don't judge it or decide if it's a good idea. Weeks or months later, often while I'm learning something completely unrelated, a fix for one of those lines clicks, and that turns into a project.

hatchzip happened exactly like that.

About a year ago I was playing a lot of games and storage was a constant fight. You download some huge compressed file, hit extract, and it tells you there isn't enough space, because extracting needs room for the archive *and* everything inside it at the same time, even though the archive is already sitting there using the space. I thought, what if you deleted the archive while you extracted it? Then I decided that was impossible and moved on, but I left it written down.

A year later, at a party, a friend said their laptop was too full to extract something. Same problem. This time the algorithm just clicked: extract from the end of the archive and cut the archive shorter after every finished batch, so the files take the archive's place and you only ever need room for what's inside.

I tried it and <span class="good">it actually worked</span>. The first version took about two hours. People started using it far more than I expected, <span class="key">a lot of them on Windows</span>, which is funny because I built the whole thing on Linux. <span class="muted">If I'd deleted that note because it was "impossible", none of it happens.</span>

Most of my other stuff came out the same way:

- [gyotaku](https://gyotaku.app) because I screenshot everything and can never find anything, so I made Ctrl+F for my screenshots folder, fully offline.
- [mytimetheirtime](https://mytimetheirtime.com) because I work with a US team from India and got tired of doing timezone math in my head. It took about an hour and was live by 3am.
- grindmap because everyone doing company-wise LeetCode prep uses the same GitHub repo of lists, and pasting URLs out of it by hand was annoying. People actually used it, which I did not expect. <span class="muted">Yes, the guy who never liked DSA prep made a DSA prep tool.</span>
- [the IITJ LAN autologin](/blogs/IITJEthernetLoginIssue) because my hostel ethernet kept logging me out every few hours.

My X bio says "I build things that annoy me until they don't," and that's about as close to a method as I have.

Paul Graham wrote about this in [How to Get Startup Ideas](https://paulgraham.com/startupideas.html). The essay opens with "The way to get startup ideas is not to try to think of startup ideas." He says the best ones are "something the founders themselves want, that they themselves can build, and that few others realize are worth doing."

<div class="callout warn">

I learned this the hard way. At one point I went the other direction and ran a whole research process to find an idea that would make money: hundreds of ideas, scored and filtered. Almost none survived, and the one I did ship from it made a few dollars. In the same couple of months, the things people actually picked up were Breakscale, hatchzip and gyotaku, and they came from my own confusion, a friend's full laptop and my own messy screenshots folder.

</div>

---

## Consistency, the small version

People hear "consistency" and picture some brutal grind. You already saw how my 16 hour days went. What works for me is much smaller.

Here are two posts of mine from one evening in September:

> had long labs and i'm dead tired, still gonna sit down and build for an hour. someone tell me this is normal :)

> told myself one hour of building. it's 11 pm. the hour started at 8 lol

That's how I actually do it. I never promise myself a big session, only one hour. Usually the hour turns into three, because once I'm inside the problem the curiosity comes back by itself. On the days it really is only one hour, <span class="key">that hour still counts</span>, and it keeps the thread from breaking.

I still slip. In August I posted "Been playing too much elden ring 😭 (Will try to be consistent from now on)." The difference now is that a bad week doesn't end the whole thing. I just pick it back up the next Sunday. I write a [weekly log](/weekly) on this site every week, good ones and bad ones. Some weeks have a launch in them. Some have an OA I bombed and a DBMS quiz I was panicking about.

The Discord journal is the clearest proof I have that consistency doesn't mean never stopping. There are gaps all over it. In August 2025 I went quiet for almost two weeks and came back with "im alive". In October it was "Uh / Im alive / Sooo / Im going college". In November: "The grind hasn't stopped, its just lazy me who hasn't been posting updates consistently." But I always came back, and <mark>sixteen months and over 3,000 messages later I'm still writing in it</mark>, including today.

The other part nobody warns you about is that <span class="bad">most of what you build will get three stars.</span> For a long time almost everything I made got close to nothing. Breakscale had 8 stars the day before I posted it, gyotaku had 2, and hatchzip had 4. If I'd needed each project to work before I made the next one, I would have quit long before any of them did.

<div class="callout good">

You can't tell in advance which project is going to be the one, so the only plan that works is to keep making the next one. That's all I mean by consistency.

</div>

---

## Post it, or nobody finds it

Curiosity and consistency get the thing built, but every opportunity I've had came from something people could see.

My job came from a post. My GSoC mentors knew my name from bug reports months before applications opened. One of Breakscale's biggest spikes came from a stranger making an Instagram reel about it, which I had nothing to do with.

When someone asked how I get reach, I said "nothing lol? i just post what i build, and people repost or quote my posts bringing me more traffic :) recursion to the max :)". That's genuinely all it is. In September I wrote "a month ago this account was basically dead," and the only thing that changed it was posting what I built, week after week.

The line I keep putting at the bottom of my posts:

> build the thing. post the thing.

The first ten times will feel embarrassing and your first launch might get three likes. Mine did. Post anyway, because <mark>the DM that changes your life comes from a repo, and only if someone can see the repo.</mark>

---

## If companies never come to your college

This part is for most of the people who DM me, because most of you aren't at an IIT or an NIT.

In 2024 the IITs had about [17,700 seats](https://www.careerindia.com/news/josaa-2024-seat-matrix-announced-17-740-seats-across-23-iits-041557.html) and the NITs about [24,200](https://www.shiksha.com/engineering/articles/josaa-2024-seat-matrix-know-institute-and-category-wise-number-of-seats-blogId-168593). That same year around [12.5 lakh students enrolled in B.Tech](https://news.careers360.com/btech-admissions-2024-2025-lakhs-seats-empty-cse-private-engineering-colleges-tamil-nadu-gujarat-karnataka-andhra-pradesh-aicte) across India. So <span class="key">more than 95 out of every 100 engineering students aren't at an IIT or NIT</span>, and a lot of them are at colleges where the big companies never show up.

If that's you, you know how it goes. You apply off campus to the big names and don't get the OA. You don't get the interview either. You get rejected at resume screening, often by a filter, before a human has looked at anything you built. That keeps happening until it feels like the door was never there.

I can't pretend I know exactly how that feels. I'm at an IIT, and the name on my resume has probably helped me in places I'll never see. But on campus my CGPA put me in a similar spot: the companies came, and the cutoff meant I couldn't sit for most of them. And for every opportunity that actually mattered to me, my college never came up.

A resume screen sorts you by college. A project that works doesn't care where you study. The DM that got me my job came from someone using Breakscale, and they never saw my resume before reaching out. Nobody filtered me out, because nobody was filtering.

Open source works the same way. When you open a PR, the maintainer sees your code and how you handle review, and nothing else. GSoC is [open to any student or open source beginner who's 18 or over](https://developers.google.com/open-source/gsoc/faq), with no list of approved colleges, and I got in because the [maintainers already knew my name](/blogs/gsoc-selection) from my contributions. People send PRs to my repos from all over the world and I've never once checked where any of them study before merging.

Small startups are similar. Big companies use filters because they get a mountain of applications. A founder scrolling X at night doesn't have one. They see a thing that works, click your profile and send a DM. That's how it happened for me.

So your public work ends up being your resume: a GitHub with real projects, a few merged PRs in repos people actually use, and posts that show you shipping week after week. None of that goes through resume screening, so it can't get rejected there.

<div class="callout warn">

This path is slower and less predictable than campus placements, and I'm not going to pretend otherwise. Most projects get three stars and most posts get no reach. But nobody has to give you permission to start, and for a lot of people it's the only door they've got. Everything else in this post works the same from any college in the country.

</div>

---

## What about AI?

I get asked this a lot too. "If AI writes all the code now, is it worth learning a language properly? Can I just learn the logic and what each function does?"

Not quite. Everyone uses AI now, companies included, all day, and I don't think many people write every line by hand anymore. I use Claude Code for almost everything. But you still have to know what's happening behind the scenes, how to fix it when it breaks, and how to check it'll actually hold up in production. AI also tends to write code that's more complicated than it needs to be, so you have to be able to read it.

hatchzip is a good example. I built it with Claude Code, and I didn't trust any of it until 120 tests passed, including tests that kill it at every commit point and check it resumes cleanly. A tool that deletes your archive while extracting it has to be right. I put it like this on X once: <span class="key">"the actual senior dev skill in 2026 is knowing when the AI is confidently wrong."</span>

You don't need to memorise every language line by line, though. The syntax is different everywhere, but underneath the ideas are the same, with a few pros and cons per language. If you've written real code before, reading AI's code won't scare you.

Tech stack still matters. AI can pick one for you if you describe the problem well, but some judgement only comes from experience. I avoid Electron for desktop apps, for example, because every Electron app ships its own copy of Chromium and it eats memory. An AI might still reach for it if you don't tell it not to, and knowing to tell it is your job.

The idea is your job too. AI helps you build it, but you're the one who noticed something wrong in your own life.

---

## If you want to start tonight

This is the part I'd actually send to the people in my DMs, and none of it needs motivation.

1. Start a problems note. Phone notes, Obsidian, a text file, anything. Every time something annoys you, even something tiny, write one line about it, and don't judge it yet.
2. When you learn something, ask how you'd *see* it. If you're reading about a cache or a scheduler or a protocol, build a tiny version you can watch work and break. That's where a lot of my projects came from.
3. Pick the smallest annoying thing on your list and build an ugly version this weekend. Leave the startup idea for later and do the small, real one.
4. Promise yourself one hour, not a whole day. On bad days one hour is a win, and on good days it turns into four by itself.
5. Post it, even if it feels embarrassing. One line on the problem, a clip of it working, and the link. Expect three likes and do it again next week.
6. Keep the "impossible" ideas. Write them down and leave them there. hatchzip was impossible for a year.
7. When a stranger opens an issue or a PR, take it seriously and reply fast. That's how a side project turns into something real, and it's where I've learned the most.

---

## The honest trade-off

Please don't drop your studies because of a blog post.

<span class="warn">My grades cost me real things.</span> Most campus placements were off the table. I went through way more rejections than I'd like, and for a long time there was no proof at all that this would work out. I got lucky with timing in places, and I know that. It also took a lot of sleepless nights and skipped meals that don't show up in any star count.

Even now, the curiosity shows up at the worst times. This week I posted that whenever midsems or endsems get close I suddenly have seven or eight crazy ideas to build, and in the replies I admitted the rest: "and then do bad in exams hehe." I'm still figuring that part out.

If the normal path works for you, take it, it's a good path. And if you can keep your CGPA up *and* build things, you'll be in a better spot than I was.

But if you're like me, and you sit down to study and end up building something instead and then feel guilty about it, I don't think that's a flaw. It tells you what you actually care about. You just have to aim it at something.

---

## One last thing

Six months ago I said a sentence I didn't believe, just so it would sound good. A small part of it has come true so far, one tired, curious hour at a time, and most days I wasn't even thinking about it. There's a lot more I want to build, and I'm still very much on the way.

So after you close this tab, skip the planning and the next video. Open your notes app and write down one thing that annoyed you today.

You don't need to feel motivated to do that. You just need to be a little curious, and then keep going.
