your github graph says you did nothing tuesday.
you actually fixed a prod incident, reviewed 3 PRs, and unblocked two people.
none of it shows up. so at review time you blank, and you feel like a fraud.
i'm building dev.log — a contribution graph for your whole work life, not just your commits. 🧵
what did you actually ship last quarter?
if you have to scroll 6 months of PRs to answer, that's a tooling gap — not a memory problem. your commit graph counts code you pushed, not the reviews, the debugging, or the fires you put out.
spent the day designing the one screen of dev.log.
a command line, not a form:
/win shipped the rate-limiter, killed the 503s
/ugh flaky CI test ate 2 hours
/til postgres FILTER beats CASE WHEN
…and it stacks into this. 👇 (mock — not built yet)
@techyoutbe the part that gets me is the performance review already said "outstanding contribution, strong leadership potential, key member of the team" — the company's own paperwork agreed with him. they just decided agreeing in writing was cheaper than agreeing in title and comp.
@YoCodingJosh the fact you had to ask claude to remember what you did all year is the whole problem in one tweet 😂 review season = archaeology for everyone. building something for exactly this (dev.log) — log it in ~10s as it happens
this is the mock of the one screen. not built yet — but this is the thing.
free forever for manual logging. building in public from zero. follow along.
your github graph says you did nothing tuesday.
you actually fixed a prod incident, reviewed 3 PRs, and unblocked two people.
none of it shows up. so at review time you blank, and you feel like a fraud.
i'm building dev.log — a contribution graph for your whole work life, not just your commits. 🧵
here's the catch: i haven't written the app yet. on purpose.
i'm finding the first 100 devs who feel this problem before i write a line of app code.
if that's you, you're early — and you get to shape it.
waitlist 👉 https://t.co/D3D6HBwl4F
the idea: one screen. you log what you did in ~10 seconds —
/win shipped the thing · /ugh fought CI for 3h · /til learned a thing · /mood fried
it lights up like a github heatmap. you can finally see the work.
🤬 ARGH, CLASSIC DEV ROOKIE MISTAKE: Built FounderHub FIRST, asked questions LATER.
Just read "The Mom Test" and... mind blown. Wasted time on AI toolkit for indie hackers thinking "build it and they come." Spoiler: Crickets! 😤
Pro tip: Talk to customers BEFORE coding castles in the sky. Who else guilty? What's your #1 Mom Test takeaway?
Rant done. Ego refactoring in progress. 🚀 #IndieHackerFail #MomTest
Trap most founders fall into: Building for 'everyone.'
Pick 1 user avatar. Map their pains, haunts, pains.
Talk to 10 this week: 'Does this solve X?'
Broad = broke. Narrow = traction. Pivot fast if no. 🎯
Saved countless launches. Your turn? 💥
#Entrepreneur#GrowthHacks
Validate your idea FAST w/ first users - no ads:
✅ Join 3 niche communities
✅ Share beta, ask feedback
✅ 1:1 calls w/ 10 users
✅ Tweak based on what they say
Manual grind > fancy tools early. 🔥
#GrowthHacking#Entrepreneur
Early founders: First 100 users? No magic, just grind.
1. Launch a simple waitlist page today.
2. Post value in 5 niche communities daily (Reddit, Discord).
3. DM 20 potentials with real questions, not pitches.
Track weekly wins. Consistency crushes. Who's in? 🚀
#Startups #FounderTips
@hustle_fred spot on, first client grind sucks longest. but $2k mrr often feels like restart when churn hits – tune retention before scaling tactics 😩💀