Writing
2026
2025
- amidst all the chaos, finding dust to build uponNisarg Thakkar6 min readamidst all the chaos, finding dust to build upon6 min read
- ideas are cheap: do market study, validate demand, ship <-> find pmfNisarg Thakkar8 min readideas are cheap: do market study, validate demand, ship <-> find pmf8 min read
- your v̶i̶b̶e̶ shit coding sucks bcs you are missing some contextNisarg Thakkar5 min readyour v̶i̶b̶e̶ shit coding sucks bcs you are missing some context5 min read
Essay
amidst all the chaos, finding dust to build upon
· 6 min read

First published on X. Read the original ↗
these are raw thoughts just observations take it as a pinch of salt just enough to balance your food, not too low, not too high.
intro: the 20s

you're in your 20s. you're a developer. random projects are your weekend vibe you're learning fast, building faster, sharing everything publicly bcs that's what "building in public" means, right?
the problem: time is finite. your ambitions are not.
you want to:
- ship 5 projects simultaneously
- maintain your full time job
- stay healthy (lol)
- have a social life
- learn every new framework
- build your personal brand
- watch anime (yes, this matters)
- touch grass occasionally
the reality: something breaks. usually it's you.
workday trap (my story)
when i shifted to blr for my first job at @Qiro_Finance, i was insanely motivated. the kind of motivated where you think sleep is optional and meals are just interruptions.
my schedule looked like:
- wake up, code
- eat whenever (sometimes 4pm, sometimes 12pm)
- work 14-16 hours a day
- company work + personal projects blend into one
- sleep 6-7 hours
- repeat
first month: felt like a superhuman. shipping code. learning fast. felt unstoppable.
after 3 months: my body said "fuck you"
random headaches. couldn't focus. eating at random times bcs "i'll eat after this function." living away from home meant no one to tell me "you need to eat actual food, not just coffee and maggi or dosa for past week."
(being gujarati, i miss my hometown and mom's food so much. some of you might not relate to the emotional attachment to home cooked food, but it's real.)
the realization: this isn't sustainable. you can run on adrenaline for weeks, maybe months. but your body keeps score. and it will collect.

chaos caln
let's break down 24 hours honestly:
sleep: 6-8 hours (let's say 7 on average)
work: 8-10 hours on weekdays (average 9)
gym: 1-2 hours, 5-6 days a week (average 1.5)
other stuff: entertainment, playing, etc (2.5 hours)
total: ~20 hours
what's left: 4 hours per weekday
multiply by 6 weekdays = 24 hours
add sunday (minus some recovery/social time) = ~14 usable hours
grand total: ~38 hours per week for "extra" stuff
now divide this between:
- personal projects
- research and learn about new things (currently for last 2 months this was my major chunk was doing turbine program for solana)
- writing articles (i have 10+ drafts sitting, waiting to be published)
- socializing (book reading events twice a month, fifa with friends)
- literally doing nothing (yes, this is important)
- sometime x streams for fun
the problem: you want to do all of this. simultaneously. perfectly.
the reality: you can't. and trying to will burn you out.
the fomo is real (but it's lying to you)
the voice in your head:
"everyone's building on aptos, you should too"
"solana is hot right now, learn rust"
"your friends are shipping on base, why aren't you?"
"this new framework dropped, you're behind"
"that guy on x just raised funding, you're falling behind"
here's what i realized: trying to learn everything = learning nothing deeply.
picking one thing at a time > half assing three things.
clarity aka dust
1. is this important to me, or just trendy?
- bad reason: "everyone on x is talking about this"
- good reason: "this solves a problem i've actually faced"
2. am i learning bcs friends are, or bcs it matters?
- bad reason: "my group chat is hyped about this"
- good reason: "understanding this will make me better at what i'm building"
3. does this relate to my full time work, or is it just hype?
- bad reason: "it's the new hot thing"
- good reason: "this connects to my company's somehow"
4. is this an interesting whitepaper, or actually useful?
- bad reason: "28 page whitepaper with cool math with buzz keywords"
- good reason: "this protocol is getting real adoption and i want to understand why"
projects: the filter

when choosing what to build, ask yourself:
is the project teaching me something new or fun?
- learn → might be worth it
- fun → probably just vibe coding
does it solve a problem i've faced?
- yes → you understand the pain point
- no → you're guessing
can i explain the problem in one sentence?
- yes → concept is clear
- research more → probably too complex or you don't understand it yet
would i use this myself?
- yes → good sign
- no → why would anyone else?
with ai tools, anyone can create a project. what matters is: do you understand the core? can you explain why it exists beyond "bcs i could build it"?
creator economy advantage
here's the thing: crypto x is creator focused now.
what this means: you don't need to jump on everything day 1.
someone else will:
- read the whitepaper
- do proper research
- make a thread breaking it down
- record a video explaining it
your job: follow people who do good breakdowns. when something excites you, then do your research. then build your project.
feedback loop
one of the most important things: asking for feedback.
but there's a right way and a wrong way.
wrong way:
- build for 5 months in secret and launch on x
- ask random people "what do you think?"
- get generic "cool project bro" replies or silence
- feel discouraged
right way:
- build mvp
- identify people who actually know this domain
- reach out respectfully and ask specific questions
- accept harsh feedback
imp: don't ask everyone. ask people who:
- you admire
- actually know the domain or have built similar things
- will give you honest (maybe harsh) feedback
asking the wrong person wastes your time or, worse, makes you pivot for the wrong reasons.
dealing with harsh feedback (the real shit)

some feedback i've received:
"you're a dev. who's going to read your articles? why are you even doing this?"
- stung at first and made me question everything
- eventually realized: i write to organize my thoughts, not for validation
"it's too technical. make it more beginner-friendly."
- valid criticism and made me rethink audience
- still figuring out the balance
"is this project for people to use, or for you to learn?"
- harsh but fair
- made me realize some projects are just for learning and that's okay
"your writing needs work. no structure"
- true and working on it
- this article is literally me trying to improve
in reality: some people won't reply. not bcs your project sucks sometime or project can sucks, but bcs they're busy.
what works:
reach out to the social/community team of projects, share your mvp with context, ask politely if [specific person] might review, make it a request, not a demand and be okay with no response
what doesn't work:
cold dm or mail: "can you review my project?", no context, just links, acting entitled to their time, getting mad when ignored
respect people's time. if they don't respond, move on. find someone else. keep building.
closing thoughts
sometimes doing nothing is best thing
seriously. scheduling time to do nothing is important.
not "scroll x/insta/substack" nothing. actual nothing.
- sit in a park
- stare at the ceiling
- let your brain process things
- exist without optimizing
your brain needs downtime. your best ideas come when you're not forcing them.
it's 2am on a random tuesday (december 23rd). i'm writing this instead of sleeping, which is ironic given the whole "prioritize health" thing.

but sometimes you need to get thoughts out. sometimes writing at 2am hits different.
if you're a dev in your 20s feeling overwhelmed:
- you're not alone
- you're not failing
- you're just trying to do too much at once
pick one thing. go deep. ship it. then move to the next thing.
the fomo will always be there. the hype will always be there. the feeling of "falling behind" will always be there.
but your health, your sanity, and your actual progress matter more than keeping up with crypto's pace.
thanks for reading. hope this helps you prioritize your work and life even 10% better than you're currently managing.
if this resonated, cool. if not, also cool. these are just one dev's thoughts at 2am.
now go get some sleep. or ship that project. or both. but definitely eat something healthy first.
ps: to the people who gave me harsh feedback thank you. you were right. i'm working on it.
pps: mom, i'm eating properly now. mostly. (she doesn't read my articles but just in case)
ppps: if you're reading this at 2am, you're part of the problem. close the laptop after this read and sleep.
Essay
amidst all the chaos, finding dust to build upon
· 6 min read

First published on X. Read the original ↗
these are raw thoughts just observations take it as a pinch of salt just enough to balance your food, not too low, not too high.
intro: the 20s

you're in your 20s. you're a developer. random projects are your weekend vibe you're learning fast, building faster, sharing everything publicly bcs that's what "building in public" means, right?
the problem: time is finite. your ambitions are not.
you want to:
- ship 5 projects simultaneously
- maintain your full time job
- stay healthy (lol)
- have a social life
- learn every new framework
- build your personal brand
- watch anime (yes, this matters)
- touch grass occasionally
the reality: something breaks. usually it's you.
workday trap (my story)
when i shifted to blr for my first job at @Qiro_Finance, i was insanely motivated. the kind of motivated where you think sleep is optional and meals are just interruptions.
my schedule looked like:
- wake up, code
- eat whenever (sometimes 4pm, sometimes 12pm)
- work 14-16 hours a day
- company work + personal projects blend into one
- sleep 6-7 hours
- repeat
first month: felt like a superhuman. shipping code. learning fast. felt unstoppable.
after 3 months: my body said "fuck you"
random headaches. couldn't focus. eating at random times bcs "i'll eat after this function." living away from home meant no one to tell me "you need to eat actual food, not just coffee and maggi or dosa for past week."
(being gujarati, i miss my hometown and mom's food so much. some of you might not relate to the emotional attachment to home cooked food, but it's real.)
the realization: this isn't sustainable. you can run on adrenaline for weeks, maybe months. but your body keeps score. and it will collect.

chaos caln
let's break down 24 hours honestly:
sleep: 6-8 hours (let's say 7 on average)
work: 8-10 hours on weekdays (average 9)
gym: 1-2 hours, 5-6 days a week (average 1.5)
other stuff: entertainment, playing, etc (2.5 hours)
total: ~20 hours
what's left: 4 hours per weekday
multiply by 6 weekdays = 24 hours
add sunday (minus some recovery/social time) = ~14 usable hours
grand total: ~38 hours per week for "extra" stuff
now divide this between:
- personal projects
- research and learn about new things (currently for last 2 months this was my major chunk was doing turbine program for solana)
- writing articles (i have 10+ drafts sitting, waiting to be published)
- socializing (book reading events twice a month, fifa with friends)
- literally doing nothing (yes, this is important)
- sometime x streams for fun
the problem: you want to do all of this. simultaneously. perfectly.
the reality: you can't. and trying to will burn you out.
the fomo is real (but it's lying to you)
the voice in your head:
"everyone's building on aptos, you should too"
"solana is hot right now, learn rust"
"your friends are shipping on base, why aren't you?"
"this new framework dropped, you're behind"
"that guy on x just raised funding, you're falling behind"
here's what i realized: trying to learn everything = learning nothing deeply.
picking one thing at a time > half assing three things.
clarity aka dust
1. is this important to me, or just trendy?
- bad reason: "everyone on x is talking about this"
- good reason: "this solves a problem i've actually faced"
2. am i learning bcs friends are, or bcs it matters?
- bad reason: "my group chat is hyped about this"
- good reason: "understanding this will make me better at what i'm building"
3. does this relate to my full time work, or is it just hype?
- bad reason: "it's the new hot thing"
- good reason: "this connects to my company's somehow"
4. is this an interesting whitepaper, or actually useful?
- bad reason: "28 page whitepaper with cool math with buzz keywords"
- good reason: "this protocol is getting real adoption and i want to understand why"
projects: the filter

when choosing what to build, ask yourself:
is the project teaching me something new or fun?
- learn → might be worth it
- fun → probably just vibe coding
does it solve a problem i've faced?
- yes → you understand the pain point
- no → you're guessing
can i explain the problem in one sentence?
- yes → concept is clear
- research more → probably too complex or you don't understand it yet
would i use this myself?
- yes → good sign
- no → why would anyone else?
with ai tools, anyone can create a project. what matters is: do you understand the core? can you explain why it exists beyond "bcs i could build it"?
creator economy advantage
here's the thing: crypto x is creator focused now.
what this means: you don't need to jump on everything day 1.
someone else will:
- read the whitepaper
- do proper research
- make a thread breaking it down
- record a video explaining it
your job: follow people who do good breakdowns. when something excites you, then do your research. then build your project.
feedback loop
one of the most important things: asking for feedback.
but there's a right way and a wrong way.
wrong way:
- build for 5 months in secret and launch on x
- ask random people "what do you think?"
- get generic "cool project bro" replies or silence
- feel discouraged
right way:
- build mvp
- identify people who actually know this domain
- reach out respectfully and ask specific questions
- accept harsh feedback
imp: don't ask everyone. ask people who:
- you admire
- actually know the domain or have built similar things
- will give you honest (maybe harsh) feedback
asking the wrong person wastes your time or, worse, makes you pivot for the wrong reasons.
dealing with harsh feedback (the real shit)

some feedback i've received:
"you're a dev. who's going to read your articles? why are you even doing this?"
- stung at first and made me question everything
- eventually realized: i write to organize my thoughts, not for validation
"it's too technical. make it more beginner-friendly."
- valid criticism and made me rethink audience
- still figuring out the balance
"is this project for people to use, or for you to learn?"
- harsh but fair
- made me realize some projects are just for learning and that's okay
"your writing needs work. no structure"
- true and working on it
- this article is literally me trying to improve
in reality: some people won't reply. not bcs your project sucks sometime or project can sucks, but bcs they're busy.
what works:
reach out to the social/community team of projects, share your mvp with context, ask politely if [specific person] might review, make it a request, not a demand and be okay with no response
what doesn't work:
cold dm or mail: "can you review my project?", no context, just links, acting entitled to their time, getting mad when ignored
respect people's time. if they don't respond, move on. find someone else. keep building.
closing thoughts
sometimes doing nothing is best thing
seriously. scheduling time to do nothing is important.
not "scroll x/insta/substack" nothing. actual nothing.
- sit in a park
- stare at the ceiling
- let your brain process things
- exist without optimizing
your brain needs downtime. your best ideas come when you're not forcing them.
it's 2am on a random tuesday (december 23rd). i'm writing this instead of sleeping, which is ironic given the whole "prioritize health" thing.

but sometimes you need to get thoughts out. sometimes writing at 2am hits different.
if you're a dev in your 20s feeling overwhelmed:
- you're not alone
- you're not failing
- you're just trying to do too much at once
pick one thing. go deep. ship it. then move to the next thing.
the fomo will always be there. the hype will always be there. the feeling of "falling behind" will always be there.
but your health, your sanity, and your actual progress matter more than keeping up with crypto's pace.
thanks for reading. hope this helps you prioritize your work and life even 10% better than you're currently managing.
if this resonated, cool. if not, also cool. these are just one dev's thoughts at 2am.
now go get some sleep. or ship that project. or both. but definitely eat something healthy first.
ps: to the people who gave me harsh feedback thank you. you were right. i'm working on it.
pps: mom, i'm eating properly now. mostly. (she doesn't read my articles but just in case)
ppps: if you're reading this at 2am, you're part of the problem. close the laptop after this read and sleep.
amidst all the chaos, finding dust to build upon
- Published
- Topic
- Personal writing
- Author
- Nisarg Thakkar
- Reading time
- About 6 min