Straight answers.

One honest line about today’s work — the decision, the stuck, the why. Two minutes, from your phone. AI writes code now, so a résumé proves less every month; dated reasoning in your voice is the signal that’s left. Nothing goes public unless you choose. See real logs →

You write what you worked through; founders read how you think, async. Open roles exist (/next/roles) — but the record is the mechanic, not the application.

Companies hiring here read how you think — not what you claim.

Skills can be taught in a quarter; what you do when nobody assigns the next step is the rare thing. “Tell me about a time you showed ownership” is rehearsed by everyone; a dated decision with its because can’t be backfilled. Your log is the gym and the evidence — it gets you read closely; nobody can promise selection.

They read for how you think: where you got stuck and how you got unstuck, a mistake and its lesson, the why behind a decision. Ten honest days makes you readable — they reach out; you don’t chase. What readers look for →

“I bombed this” · “I was wrong” · “I’m stuck”. Proof is private by default — no feed, no comments, nothing public until you open your URL at Day 30. The only readers are founders and engineering leaders, and honesty about being stuck is exactly what they read for.

Learn here, network elsewhere. You write what you actually worked through, privately — writing the whydaily is what sharpens the thinking, and the record it leaves is proof of how you think. Once you’ve learned here you can bring others — a mentor link, your own readers. No streaks; you log when you’ve worked through something worth keeping.

Build-in-public is performance — an audience and claps. Proof is private: the stuck, the wrong calls, the why. Founders read it async and reach out when hiring — you stop applying; the work comes to you.

You interview better (your “when I got stuck” answers are already written), decide more clearly (the why forces it), write clearer prompts, and bank a dated record that’s yours forever. Day 30 opens an optional public URL — on your terms.

Ten days of daily writing is a hard filter (most signups never cross it), so the pool stays small; structured logs read in minutes. AI screening résumés is the disease — we don’t cure it by AI-screening logs.

He curates /sampleand writes back on your entry when you ask him a question. On scale, honestly: the ten-day filter does most of the work, and founders read the pool directly too. If one reader ever isn’t enough, the answer is more human readers — not an AI screen. Who is RK? →

RK taught programming for 15 years — the last 8 teaching Indian engineers how to learn— and Proof is that offline practice turned into a system. No Product Hunt, no paid acquisition; people arrive through the teaching, the book, and each other. Retention isn’t engineered either — no streaks, no badges, on purpose: the practice pays you first.

DECIDED, LEARNED and CHANGED MIND ask for it directly; on BUILT it’s the second line — what you skipped and why. Every entry with a because counts, several a day all count; the role card shows your exact targets.

“I didn’t build the browser extension because the site version came first.” Tradeoffs are reasoning; readers value them as much as the build itself.

It changes what gets read first, not the interview itself. Founders read your daily log async and reach out when the thinking fits a role — instead of you applying into a stack of open tabs. And writing the why daily makes you sharper at articulating how you think; that’s yours to keep, job or no job.

The pool counts your days inside your own rolling 20-day window; if your ten honest days land while the role is open, you’re in. If it closes first, nothing is wasted — you’ve banked WHYs and a dated record every future role reads the same way. Write Day 1 →

Founders read the pool and reach out to the thinking they want. Nobody can promise selection — anyone who does is selling something.

48 founders and leaders read this pool; the opportunity that finds you may not be the one that was announced.

Founders read async, when they’re hiring; interest arrives when your thinking meets a real opening. What’s promised is narrower and real: cross the 10-day filter and you get read. Anyone promising you a date is selling something.

Every role belongs to a specific company; office, remote, and city are that company’s call — on the role card, settled directly with the founder once they reach out. No recruiter sits in between.

Every decision in your own project is yours. “Chose X over Y because…”, “skipped tests today because…” — that’s what you internalize forever, and what a hiring manager reads for tradeoffs.

You type into ChatGPT to get the machine’s words. You type into Proof to put your words on record — dated, locked the next morning, never rewritten by anyone. No model answers you, no model edits you; humans read what you wrote.

A log is written before you know who’s reading. To game it you’d have to fake real reasoning, dated, for weeks — which is just buildingthe reasoning. And in the interview, “you wrote this on Day 12 — walk me through it” catches a fabricator in minutes. The strongest signal is honesty about being stuck; the struggle is the point.

Open it from the confirmation screen or your record: change the wording, fix a typo, add a link. After it seals it’s locked word for word and dated — so nobody (including you) can rewrite history to fit a role later. Write honestly today; you have until morning to tidy it.

Write one thing you learned as a stuck or decided entry in your own words, then attach the article with + attach a link. The log is the reasoning — what you got stuck on, what you chose and why; the blog is the evidence a reader can open. Your post stays yours, wherever it lives.

Logging is deliberately low-friction so you can write the moment something happens. Founders and leaders dosign in — they log in to read the work and reach out. You don’t apply to them; you keep a record, they read it async, and when your thinking fits what they’re hiring for they come to you. The login that matters for hiring is theirs, not a wall in front of yours.

If you’re strong and still stuck, the leak is usually the channel, not you. Applications filter on keywords and titles; the thing that’s actually scarce now — judgment, the calls you made and why — never reaches a human before an ATS or a recruiter screens you out. Proof inverts that: founders and leaders read your dated reasoning async and reach out, with no application in the way. It won’t manufacture a role, and anyone who promises you one is selling something — but it puts the part of you a résumé can’t carry in front of people who hire on exactly that.