prachi
Developer · writing since 28 Jun
Day 2 of 30
Day 52 · public proof
How prachi thinks
Decides and owns the call — moves before being told.
↳the log that shows itarticulate·curious·decisive
◈ Open to being sharpened⤳ Sharpens others · 1
How prachi think, mapped · lit by their own logs · 7 showing
How you reason · the four moves
Evidence
argue from what you saw, not what you assumed
Alternative
name the option you didn't take
Assumption
surface what you're taking on faith
Tradeoff
state the cost of the call
How you work · the qualities founders read for
Curious
you ask, not just assert
Articulate
you write the full why
Ownership
you own the call & the miss
Showing — it’s in their logs; tap to see them allno %, no rank — evidence, not a score.
Milestones3 earned
Day 30 · Jul 31Day 20 · Jul 20Day 10 · Jul 09
The climbYou climbed.
The shape of your 48 entries
beta · being tunedYou climbed.
30 Jun → 18 Sept
up when you grow · flat when you hold steady · a dip when you go quiet — it’s the shape of your work, not a score.
up when you grow · flat when you hold steady · a dip when you go quiet — it’s the shape of your work, not a score.
Why this is the brag
Then you were stuck on icons!.
Now: stuck on Render deployment of agent — worker….
Now: stuck on Render deployment of agent — worker….
↑ You're stuck on a harder thing now, not the same one. That's real growth.
Every valley named in your own words. Nobody can fake a climb.
About
React NativeJavaScriptTypeScriptReact
prachi · the character an interview can’t show
48 logs over 12 weeks — read from their own words.
+ Only points upShown so far: Honest when it's not working, Adjusts and Makes the tools better.
Character · what an interview can’t reach
✓Shown
Honest when it's not working
5 stuck and 0 hard days, logged plainly instead of hidden.
Proof · from their own logs
9 Jul
15 Jul
25 Jul
✓Shown
Adjusts — updates when the evidence changes
Changed course 2 times in the open, with the reason written in — not dug in.
Proof · from their own logs
2 Jul
25 Jul
◇Not yet
Lifts other people's work
Reads plenty (53 reactions) but hasn't yet weighed in on anyone's thinking — not a mark against them, just not yet on the page.
✓Shown
Makes the tools better
3 reports they filed got fixed — they improve what they use, not just what they're paid to.
Proof · reports they got fixed
20 Aug
4 Aug
4 Aug
The judgment behind it ↓
And the technical judgment holds up
Evidence3
Alternative10
Assumption7
Tradeoff2
About 2% of engineers on Proof reason across all four. Keep the tradeoffs coming. This is the easy read — an interview catches it too. The character above is the part it can’t.
The arc · they didn’t start here
Early
165
character whys
→
Lately
0
steady
Showed up · 32 days
5 stuck + 0 hard days, logged anyway. Nobody farms honest bad days — that’s why this counts and a streak doesn’t.
A hard day, in their words
running the expo app often leads to crashing...which sometimes gets resolved by tunneling (but often tunneling fails with ngrok error) someone who's worked on expo maybe could hel
Read prachi’s logs →sign in to connect with them
Recent logs30
Mistake25 Jul 2026
#5: Change a tutorial, log
Tried to build a currency converter mobile app today by myself first and got stuck on props.
Wrote:
```
const renderItem = (item: Currency) => { ... }
```
and passed renderItem to FlatList assuming FlatList would pass just the Currency item directly
FlatList internally calls renderItem with an object shaped like {item, index, separators}
so, item should be destructured out of it.
the correct approach would be
const renderItem = ({ item }: { item: Currency }) => { ... }