Animesh
Product engineering at an early stage startup · Bangalore · writing since 21 May
Day 101 · public proof
Their logs30
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
WhyHigh agency + competency + experience is the bar - you need to know how stuff can go wrong and what's the fastest way to fix that.
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
◈ Open to sharpen
6 months on Proof
■ weeks with logs■ quiet week
141 logs · 81 say why
How Animesh thinks
Decides and owns the call — moves before being told.
↳the log that shows itarticulate·curious·decisive
◈ Open to being sharpened⤳ Sharpens others · 26
How Animesh thinks, mapped · lit by their own logs · 8 showing
How they 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
What their logs say
Curious
you ask, not just assert
Articulate
you write the full why
Ownership
you own the call & the miss
Persistent
hard things become lessons
Showing — it’s in their logs; tap to see them allno %, no rank — evidence, not a score.
Milestones3 earned
Day 30 · Jun 19Day 20 · Jun 09Day 10 · May 30
About
JavaScriptRubyPostgresMySQLAWSReactRails
🎓 maharaja surajmal institute
Projects
fplaunchpad.org
fplaunchpad.org ↗Why · from their logbecause it's a better use of my time that way.
1 logRead the log ›
GitHub
GHgithub.com/Animesh-Ghosh ↗Repos show when they’re linked from a log. Proof doesn’t count stars or commits.
Want a page like this?
Write what you tried, a few lines a day. People who’d hire you read it.
Start your Proof





