The Unread Pile — Edition No. 5

Tuesday, 29 September 2026 · MumbaiEdition No. 526 new posts · 14–28 Sep

Lead Feature · Thirty years of Shaadi.com

The $100 Domain That Outlived Everyone Who Said It Was Too Early

By @Rahul_J_Mathur · 25 Sep · a three-post thread cataloguing Manish Jain’s oral history

On 30 July 1996, Manish Jain paid $100 and registered a domain name in a country with 4.5 lakh internet users. Four years later he sold it — to a buyer who sold it to another buyer — and the company that ended up owning it waited a full decade before raising its first venture round. Thirty years on, Shaadi.com is a marriage-market institution, and the thread reads less like company lore than a counter-example to every “too early” verdict you’ve ever heard.

Stacked old books — thirty years of internet history — Thirty years of Indian internet, stacked like old books. The market Shaadi.com was built for arrived a decade after the product did.

The details, reconstructed from Manish Jain’s own recollections, are almost absurd. Version one was built in 1996, when India’s entire internet population would barely fill a Mumbai suburb. By the time he sold it in 2000, the user base had grown to 56 lakh — which sounds like progress until you realise that was 0.5% penetration. Then the money detail: when People Interactive bought the business in 2001 for $25,000, that sum was 83% of the company’s cash. They spent nearly everything they had on a domain, a database of profiles, and a belief that Indians would eventually find spouses online.

Shaadi.com: the timeline of being early

Timeline reconstructed from Manish Jain’s oral history, via @Rahul_J_Mathur; blog catalogued at celestri.org.

The ownership chain is its own lesson in patience. Manish sold to Siddharth Mehta, who sold to Anupam Mittal — who had himself started a matchmaking site, Sagaai.com, back in 1997. And then the quiet statistic that should make every founder wince or rejoice: Anupam raised his first venture round ten years after starting. The business grew inside a market that was itself growing at 0.5% penetration — which meant the strategy was not “capture the market” but “survive until the market exists.” By the Wharton era of the story, India had 14.2 crore internet users (11% penetration), and the domain bought for $100 had become one of the most defensible brands in the country.

“Anupam was early. Manish was even earlier.”— @Rahul_J_Mathur, on thirty years of Shaadi.com

$100

paid for the domain, 30 Jul 1996

4.5L

Indian internet users in 1996

83%

of company cash spent on the 2001 acquisition

10 yrs

before the first venture round

Main learnings

Being early is a cash-flow problem, not a vision problem. The bet was correct in 1996; the company only became financeable around 2006. Survival was the strategy.
Conviction can be measured in percentages of cash. 83% of company cash on one acquisition is the kind of concentrated bet memos romanticise and treasuries forbid.
Founders sell to believers, not just buyers. The chain Manish → Siddharth → Anupam worked because each handoff kept the thesis alive. Domains outlive their original registrants; theses outlive their original founders.
Delayed gratification compounds at the market’s pace, not yours. Anupam’s ten-year wait for venture money is the PBD line from this edition’s sidebar, rendered as company history.

Practical takeaway — If you’re building for a market that doesn’t exist yet, budget for survival measured in years, not quarters — and treat every $100 decision as though the next owner of it might be a thirty-year institution.

Originals: Thread 1/3 · Thread 2/3 · Thread 3/3 · Full oral history catalogued at celestri.org

Inside this edition · 23 stories

Lead
Shaadi.com at 30
Money & Markets
Kissht vs MoneyView IPOs
AI & Builders
Explainer videos for repos
Sherpa: Pocket FM’s fiction AI
Your laptop is a web host
AGENTS.md in Claude Code
Startup Strategy
Expose endpoints to agents
Barbell-ification of software
Onboarding tells the story
Ship sooner than ready
Your brand is 10 people
Muse as a GTM weapon
Career & the Inner Game
Resumes miss the context
Uncertainty tolerance
Astra 6’s new law
Why evenings evaporate
Character is slow success
Briefs
Apple’s wish-list · Bolt Forge · Self-pity · Muse the colleague · HP, Bollywood edition · Embarrassment

Quote of the day

“The best thing that can happen to your character is that success takes longer than you wanted.”

— Patrick Bet-David, via @vaibhavbetter

Thirty years, one arc

30 Jul 1996
$100 domain — 4.5L users online

1997
Sagaai.com — Anupam’s parallel bet

2000
First sale — 56L users, 0.5%

2001
$25,000 — 83% of company cash

~2006
First VC — ten years in

Today
Institution — an Indian verb

Money & Markets

Are Digital Lenders Really Lenders?

By @Rahul_J_Mathur · 28 Sep · IPO comparison thread: Kissht vs MoneyView

Two digital lenders hit the public market within months of each other, and the thread that matters this week argues you should read one of them as a lender and the other as a loan factory with someone else’s balance sheet. Kissht listed on 8 May 2026 and is up 105% from its IPO band; MoneyView opens today with a grey-market premium of ~42%. The surface stats look like siblings — RoE 24% vs 17.9%, GNPA 2.16% vs 2.74%, price-to-book 2.7× vs 2.3× — but the business model underneath is a completely different animal.

Candlestick chart on a screen — The tape says both are “fintech lenders.” The balance sheet says otherwise.

The thread’s core distinction is the off-book ratio. Kissht is a lender: roughly half its AUM sits off its own balance sheet. MoneyView is, in the author’s framing, an originator: about 75% of its AUM is off-book — someone else funds the loans; MoneyView makes its money originating and servicing them. That single ratio reframes everything else. MoneyView runs 3× the overall AUM of Kissht, but on-book it holds only ₹5,650 crore against Kissht’s ₹3,500 crore — a far smaller gap than the headline AUM suggests. And because Kissht carries more of the risk itself, its balance sheet is the healthier of the two.

Kissht vs MoneyView — the numbers the IPO band hides

Thread data: FY26 normalised PAT ~₹397 cr for MoneyView; Kissht listed 8 May 2026. Not financial advice.

Here’s the bull case the thread actually builds: the market is mispricing the origination business. MoneyView trades at a PEG of 0.3× against Kissht’s 1.1× — the originator model is being valued like a boring lender while growing like a platform. If MoneyView shifts more of its AUM on-balance-sheet, the re-rating could be sharp, because every basis point of spread then accrues to its own book instead of a partner’s. The overhangs are real though: questions around CEO compensation and a recent cyber incident, both of which the thread flags before the disclosure does its work — the author applied under the HNI quota and holds no Kissht, and none of this is financial advice.

“Buyer Beware. Not all digital lenders really lenders!”— @Rahul_J_Mathur, opening the thread

+105%

Kissht since IPO band (8 May 2026)

~42%

MoneyView grey-market premium

75%

MoneyView AUM off-book (originator)

0.3×

MoneyView PEG vs Kissht’s 1.1×

Main learnings

Read the off-book ratio before the P/E. “Digital lender” is a category; lender vs originator is the business model. The ratio tells you who bears the credit risk.
AUM comparisons are meaningless across models. 3× the total AUM collapses to a much smaller gap on-book. Compare the book, not the funnel.
The mispricing thesis is a migration thesis. MoneyView is cheap only if you believe origination earnings will eventually sit on its own balance sheet.
Flag the governance items first. CEO comp and a cyber incident sit in the same thread as the bull case — that’s the correct order.

Practical takeaway — Before touching any fintech IPO: find the off-book percentage in the RHP. Above ~50%, you’re buying a distribution business priced as a lender — value it accordingly.

Original: @Rahul_J_Mathur’s Kissht vs MoneyView thread

AI & Builders

Every Open-Source Repo Deserves an Explainer Video

By @deedydas · 28 Sep · a 7-minute SQLite video, generated by Opus 5.5 + Gemini 3.8 TTS

The pitch is simple enough to be a manifesto: every open-source repository on GitHub should ship with a generated explainer video. The proof is a seven-minute video on SQLite — one of the most-read, least-understood codebases on earth — produced by an Opus 5.5 + Gemini 3.8 text-to-speech pipeline, and it’s structured like a masterclass in reading other people’s code.

The video runs five acts, and the sequence is the insight. One: what the repo actually does, in plain language. Two: a high-level code map — where things live. Three: the life of a query, end to end. Four: the core abstractions, the mental models the codebase assumes you already hold. Five: a real execution trace, including SQLite’s join-order query planning — the moment the abstract becomes a concrete sequence of decisions. It’s a pedagogy that mirrors how seniors onboard juniors: purpose, map, flow, mental models, then a real trace.

Anatomy of a generated explainer — five acts, one codebase

Structure of the SQLite explainer video (Opus 5.5 generation, Gemini 3.8 voice).

“Everything truly is code.”— @deedydas, on what a good explainer makes you see

Main learnings

The pipeline exists now. A frontier model plus TTS can turn a repo into a watchable lesson — documentation-as-video is a generation problem, not a production problem.
Structure is the pedagogy. What → map → life-cycle → abstractions → real trace is a reusable onboarding grammar for any codebase.
Trace beats tour. The fifth act — a real execution trace through query planning — is what separates an explainer from a README read aloud.

Practical takeaway — Next time you inherit a repo: prompt a frontier model for the five-act explainer in text form first (what, map, lifecycle, abstractions, one real trace). It’s the cheapest senior-dev onboarding you’ll get.

Original: @deedydas’s SQLite explainer video

Sherpa: The Fiction-Writing AI Behind Pocket FM’s $500M ARR

By @RohanNayak2 · 19 Sep · inside Pocket FM’s creative machine

Pocket FM went from $250 million to $500 million in annual recurring revenue by lifting content production 1,200% in a single year — and the engine behind it is Sherpa, a fiction-writing AI trained on 5.5 billion hours of playtime. This is not a writing assistant. It’s an industrial story factory with 550,000 creators, 2.6 million annualised hours of audio, ten per cent of eligible writers earning over $200,000, one blockbuster crossing $100 million in revenue, and three writers turned millionaires in under two years.

Speaker on stage — The numbers that make storytellers nervous: 5.5 billion hours of training playtime, 550K creators, and a blockbuster that earned $100M.

Three technical leaps make Sherpa more than a prose generator. First, a narrative world model — a semantic knowledge graph tracking characters, plots, and continuity, so a 500-episode serial never forgets who killed whom in episode twelve. Zero continuity decay, the failure mode that kills long-form AI fiction. Second, a hierarchical story planner that decomposes season → arc → sequence → episode → scene, with dynamic replanning when a plot thread goes slack. Third, a prose engine trained on over a billion tokens of retention data, scored against a 40-item evaluator checklist that matches human judgment 80–90% of the time. Retention, not fluency, is the fitness function — the model learns what keeps a listener past episode three, not what reads prettily.

The Sherpa pipeline — seven steps from idea to global monetisation

Pipeline and economics via @RohanNayak2; figures are Pocket FM’s disclosed ARR/creator stats.

1,200%

content production lift in 1 year

5.5B

hours of playtime trained on

$500M

ARR (up from $250M)

550K+

creators on the platform

Main learnings

Continuity is the moat in long-form generation. The world model exists because the failure mode of AI serials isn’t bad prose — it’s forgetting. Knowledge graphs solve what scale alone doesn’t.
Train on the outcome, not the craft. A billion tokens of retention data optimises for the metric that pays — listeners who come back — not for literary taste.
Evaluators are the product. A 40-item checklist matching humans 80–90% of the time is what lets one-tap production exist at all. The generator is commoditised; the taste function is the asset.
Creator economics close the loop. Three millionaires in two years is not PR — it’s the flywheel’s fuel, pulling more creators into a better model.

Practical takeaway — For any AI product: identify your version of “continuity decay” (the failure mode scale doesn’t fix), build an evaluator that matches human judgment before you scale generation, and optimise for the retention metric, not the aesthetic one.

Original: @RohanNayak2 on Sherpa

Your Laptop Is Now a Website Host

By @dale_vaz & @suganthan · 20 Sep · Cloudflare’s free tunnel at try.cloudflare.com

Cloudflare launched a free service — no account, no signup — that turns any website running on your localhost into a public, secure, shareable URL. It is the ngrok-killer with the friction removed: point it at your local port, get a real URL, share it. Prototypes stop dying in screen-shares.

Phone glowing against a night city — Localhost, meet the internet: the tunnel goes from your machine to a public URL in one command.

The mechanism is a tunnel: your machine opens an outbound connection to Cloudflare’s edge, and Cloudflare routes public traffic back down that connection to your local server. Because the connection is outbound, there’s no port-forwarding, no router configuration, no firewall hole — which is why it works on café wifi. The contrast with ngrok is the business model: ngrok’s free tier is deliberately limited (expiring URLs, session caps) to convert you to paid; Cloudflare gives the tunnel away to put you inside its network, where the upsell is everything else Cloudflare sells.

How the tunnel works — no inbound ports, no account

After the try.cloudflare.com launch notes, via @dale_vaz and @suganthan.

Main learnings

Outbound is the trick. Firewalls block inbound, not outbound — the tunnel rides the direction traffic is already allowed to go.
Free is a distribution strategy. Cloudflare can afford free tunnels because the tunnel is the top of a funnel that ends in Workers, R2, and Access.
Prototypes get shared or they die. The demo gap — “it works on my machine” — is a collaboration tax; one command removes it.

Practical takeaway — For the next prototype you’d otherwise screen-share: run it through try.cloudflare.com and send the link instead. Feedback on a live URL beats feedback on a screenshare.

Originals: @dale_vaz · @suganthan

AGENTS.md Lands in Claude Code

By @trq212 · 18 Sep · v2.1.277

Claude Code v2.1.277 made AGENTS.md a first-class citizen: when no CLAUDE.md is found, the harness now falls back to AGENTS.md, with a toggle in /config. It’s a small diff with a large signal — the ecosystem converged on a filename, and the tool followed the convention rather than defending its own. Built, fittingly, on Claude Code mods (custom harness instructions), the very mechanism AGENTS.md exists to describe.

The fallback — convention wins over branding

Claude Code v2.1.277 release notes, via @trq212.

Practical takeaway — If you maintain agent instructions in a repo, standardise on AGENTS.md. The tools are converging on the name; your instructions now travel across harnesses.

Original: @trq212 on the AGENTS.md fallback

Startup Strategy

Expose Endpoints to Agents

By @paraschopra · 19 Sep · a growth hack for the agent era

The easiest growth hack of the next era, per Paras Chopra: take the utility currently locked behind “contact us” and a human signup, and expose it as an endpoint AI agents can call. The agents become a distribution channel — and because agents can make micropayments for costly services, the endpoint pays for itself while abuse stays priced out.

The mechanism is worth spelling out. Most B2B value is gated by sales friction: a demo call, a contract, a procurement cycle. An agent doesn’t need any of that — it needs an API key and a price. By pricing the expensive operations in micropayments, you convert the abuse problem into a revenue line: every call that would have been spam becomes a transaction. The flywheel turns on its own: business value becomes an endpoint; agents discover and call it; micropayments fund the capacity; more capacity invites more agents.

The endpoint flywheel — agents as a distribution channel

After @paraschopra’s thread; the abuse-pricing point is the hinge of the argument.

Main learnings

Sales friction is the moat’s lock; the endpoint is the key. Anything gated behind a human process is invisible to agents — unlock it and you gain a channel that never sleeps.
Price the abuse vector. Micropayments turn the spam problem into the revenue model; cost is the rate limiter.
Agent distribution compounds. A human signup is one conversion; an agent integration is a conversion that calls you back forever.

Practical takeaway — Audit your product for “contact us” gates. For each one, ask: what would the agent-callable version look like, and what micropayment would make abuse profitable instead of painful?

Original: @paraschopra’s endpoints thread

Build the Whole Platform

By @gokulr · 16 Sep · quoting Vernal’s “Moats & the Barbell-ification of Software”

As the cost of creating software collapses toward zero, the market splits into a barbell: commodity features on one end, platforms on the other, and a hollowed-out middle. Gokul’s distillation of the Vernal essay is blunt: if you’re not the platform, you’re a feature on someone else’s platform — and features are exactly what AI now generates for free.

The barbell-ification of software — the middle gets hollowed out

After Vernal’s “Moats & the Barbell-ification of Software,” via @gokulr.

Main learnings

Zero creation cost doesn’t zero value — it relocates it. Value flows to the scarce layer: distribution, trust, the transaction layer agents actually call.
The middle is the danger zone. A “good product” that isn’t a platform and isn’t free is precisely what a prompt can now replicate.
Own the layer agents transact on. Read with the Paras Chopra story above: the endpoint layer is the platform layer in the agent era.

Practical takeaway — For every product you own, place it on the barbell. If it sits in the middle, the roadmap has two honest exits: become the platform, or become the free commodity nobody competes with.

Original: @gokulr on the barbell-ification

Onboarding Is Where You Tell Your Product’s Story

@a16z · 16 Sep · Josh Elman on a16z.news

Twitter, 2009: millions signed up, landed on a blank screen asking “What’s happening?”, understood nothing, and never came back. The fix wasn’t a feature — it was onboarding rebuilt to teach one core concept at a time, and it moved retention more than anything else the company shipped that year. And in the same edition, the a16z line that belongs stapled to it: “AI has collapsed the cost of building products, but not the cost of knowing what to build.”

The two points are one thesis about where value hides when building is cheap. The 2009 Twitter failure was a comprehension failure: the product existed, the concept didn’t land, so the funnel leaked at comprehension, not at acquisition. Teaching one concept at a time — follow five people, see a timeline, understand the loop — repaired the leak at its cheapest point. Elman’s lesson generalises cleanly to the agent era: when anyone can build the thing, the scarce resource is the user’s understanding of what the thing is for. Knowing what to build — and making the user know it in the first ninety seconds — is the moat that survives free creation.

“AI has collapsed the cost of building products, but not the cost of knowing what to build.”— @a16z, the sentence that rhymes with the 2009 story

Main learnings

Retention leaks at comprehension, not acquisition. The 2009 signup millions were won and then lost on a blank screen.
One concept at a time. Onboarding is a story told in chapters, not a feature tour.
Cheap building raises the price of knowing. The a16z line is the barbell essay’s twin: judgment is the scarce input.

Practical takeaway — Watch a new user’s first ninety seconds. If they can’t state what your product is for in one sentence, no amount of shipping fixes it.

Original: @a16z / Josh Elman on onboarding

Ship Sooner Than Ready

By @tankots · 15 Sep

The perfection mindset has a known failure mode: a year passes, nothing ships. The counter-loop is four words long — ship fast, get real feedback, improve, ship again — and it compounds, because each turn of the loop buys information the previous turn couldn’t have predicted.

Team gathered around a whiteboard — The loop in its natural habitat: a whiteboard, a team, and a bias for shipping.

The ship loop — the compounding machine

The loop, after @tankots; the alternative is a year of polishing and zero information.

Practical takeaway — If a launch has been “almost ready” for a month, the missing ingredient isn’t polish — it’s the first turn of the loop. Ship the embarrassingly small version this week.

Original: @tankots on shipping

Your Personal Brand Is 10 People

By @warikoo · 15 Sep

Everyone is already a personal brand; the only variable is how many people know of you. Ankur Warikoo’s reframe cuts the ambition down to a tractable unit: start with the ten people who could recommend you for the work you want. What have they seen you do? Being known by them, for something specific, is a perfectly worthwhile beginning.

Founder looking out of an office window — Start with ten. An audience is a decision you make later — or never.

The mechanism is reputation as a routing problem. Opportunities don’t arrive from audiences; they arrive from ten specific humans who, when a role or a project surfaces, think of your name for one specific thing. “For something specific” is the operative phrase — diffuse fame doesn’t route; specificity does. And the sequence matters: the ten come first, the audience later, and only if you want one. Most people invert this, optimising for reach before they’re known for anything, and end up famous to no one who can hire them.

“You can decide later whether you also want an audience.”— @warikoo, on the ten people who matter

Main learnings

Brand is a count, not a quality. The difference between you and a “personal brand” is arithmetic: how many people know of you, and for what.
Specificity routes opportunities. “Known for something specific” is what makes a recommendation possible; vague admiration isn’t actionable.
Sequence the ambition. Ten recommenders first, audience optional. Reach without specificity is noise.

Practical takeaway — Write the ten names. Next to each, write the one specific thing you want them to have seen you do. Anything on that list you haven’t done yet is your actual personal-brand roadmap.

Original: @warikoo on the ten people

Muse as a GTM Weapon

By @DavidPawlan · 15 Sep · a consumer-brand playbook

The playbook: find a competitor’s Instagram posts, pull the list of people who liked them, DM each of them a promo — all of it automated. David Pawlan’s thread packages it as a consumer-brand GTM weapon, and the uncomfortable part is how well it should work: a like is a declared interest, and a DM is a conversation. The caveat travels with the tactic: rate limits need strategy. Automate the targeting, throttle the outreach, stay inside the platform’s tolerance — or the weapon fires once and gets your accounts flagged. It’s growth hacking with a tripwire attached.

Practical takeaway — Intent data beats demographic data: people who liked a competitor’s post are the warmest audience in the funnel. But treat rate limits as a design constraint, not an afterthought.

Original: @DavidPawlan’s GTM playbook

Career & the Inner Game

Resumes Miss the Context

By @anujrathi · 28 Sep · on his Hindustan Times piece

A resume records where you worked and what you achieved. The judgment behind those outcomes — why that decision, with that information, at that moment — stays with the people who saw the work up close. Anuj Rathi’s Hindustan Times argument: AI can make that context portable, so professionals get understood beyond their immediate networks.

Fountain pen and journal — The resume is the what. The judgment is the how. Only one of them travels today.

The mechanism is a missing layer. Hiring today reads the outcome layer (titles, metrics, exits) and guesses at the judgment layer — was it skill or luck, agency or tailwind? The guess is outsourced to references, backchannels, and the prestige of the logo on the page, which is why talent gets mispriced across networks: the same judgment reads as brilliance inside the room where it happened and as a bullet point outside it. Rathi’s thesis is that AI collapses the cost of capturing the judgment layer — decision logs, context trails, the reasoning behind the outcomes — and makes it portable. The resume stops being a credential and becomes a window: not just what you did, but how you thought, readable by strangers.

The two layers of a career — and what AI makes portable

After Anuj Rathi’s Hindustan Times piece, via @anujrathi.

Main learnings

Outcomes are public; judgment is private. The resume captures the half of the story that’s easiest to verify and hardest to learn from.
References are lossy compression. Backchannels exist because the judgment layer has no portable format — yet.
Capture the how while it’s fresh. Decision logs written in the moment beat reconstructed narratives every time.

Practical takeaway — After any significant decision, write one paragraph: what you knew, what you chose, and why. It’s the beginning of a portable judgment layer — and the cheapest career asset you can build.

Original: @anujrathi on the Hindustan Times piece

Uncertainty Tolerance

@PromptLLM · 15 Sep, reframed by @anujrathi · 16 Sep

“‘Uncertainty tolerance’ is the greatest indicator for your quality of life.” The claim: every wisdom tradition and modern neuroscience converges on the same variable — how well you sit with not knowing determines how well you live. Anuj Rathi’s reframe adds the second ingredient: the ability to tolerate pain, minus the “the world ought to be this way” syndrome.

The mechanism is compounding under ambiguity. Most high-value bets — careers, companies, relationships, investments — pay out on timelines longer than your certainty horizon. If you need certainty to act, you take only the bets whose outcomes are already priced in, which means you harvest other people’s leftovers. Tolerance for uncertainty lets you act on positive expected value while the variance is still live; the “ought” syndrome is the tax — suffering not from the outcome but from the gap between the outcome and your model of how the world should behave. Remove the ought, keep the tolerance, and you can keep making good bets through the stretches where good bets look like mistakes.

Uncertainty tolerance — the compounding variable

After @PromptLLM and @anujrathi’s reframe (15–16 Sep).

Practical takeaway — When a decision feels unbearable, check which half hurts: the actual uncertainty, or the “ought” — the story that it shouldn’t be this way. You can only act on the first.

Originals: @PromptLLM · @anujrathi’s reframe

Astra 6’s New Law

@PromptLLM · 16 Sep · an AI-proposed principle

An AI model proposed its own law of goal achievement: “The cost of achieving a goal depends heavily on how early you let reality correct you.” The cheaper the feedback loop, the cheaper the goal. Delay the correction and you pay compound interest on the error.

It’s the same mathematics wearing different clothes as the ship-fast loop two sections up. Every goal has an error term — the gap between your model and reality — and the error grows the longer it runs uncorrected, because each subsequent decision compounds on the wrong base. Letting reality correct you early is not humility; it’s arithmetic. The suggested morning habit that travelled with the principle: start the day by asking what reality might already be trying to tell you — check the metric, read the feedback, look at the thing you’ve been avoiding — before the day’s decisions stack on top of yesterday’s uncorrected model.

“The cost of achieving a goal depends heavily on how early you let reality correct you.”— Astra 6’s proposed law, via @PromptLLM

Practical takeaway — Morning habit: before planning the day, spend five minutes on the cheapest available reality check — the number, the message, the feedback you’ve been postponing. Correction is cheapest at dawn.

Original: @PromptLLM on Astra 6’s law

Why Your Evenings Evaporate

By @Tim_Denning · 28 Sep · the neuroscience of post-work fatigue

The plan was exercise, a chapter, a real meal. The outcome was the sofa, the phone, and the vague guilt of another evening that evaporated. Dr. Dominic Ng’s “Why You Waste Your Evenings” — surfaced by Tim Denning — names the mechanism: by evening, your decision-making budget is spent, and the sofa is not a failure of character but the predictable output of an exhausted executive function.

The mechanism is ego depletion wearing a workday. Every decision, interruption, and act of self-control through the day draws down the same finite pool of executive resources; by 7pm the pool is dry, and the brain defaults to the lowest-effort available stimulus — the scroll, the stream, the snack. Willpower at 8pm is a strategy built on a resource that no longer exists. The takeaway inverts the usual advice: don’t plan to decide better in the evening — design the evening before it starts. The meal is planned in the morning, the workout clothes are out, the book is on the pillow. You remove decisions from the evening the way you remove friction from onboarding: the behaviour you want is the behaviour with zero activation cost when you’re depleted.

Main learnings

Evenings fail by design, not by character. Depleted executive function defaults to the cheapest stimulus — that’s neuroscience, not laziness.
Willpower is a morning resource. Budgeting 8pm willpower is spending money you don’t have.
Design beats decide. Pre-commit the environment (planned meal, laid-out clothes, book on pillow) so the good evening costs zero decisions.

Practical takeaway — Tonight’s evening gets designed this morning: one meal planned, one movement cue placed, one screen-free object positioned. Three decisions now replace thirty you won’t make later.

Original: @Tim_Denning on the evening trap

Character Is Slow Success

By @vaibhavbetter · 20 Sep · Patrick Bet-David

The best thing that can happen to your character is that success takes longer than you wanted. The line earns its place as this edition’s quote of the day because the whole front page is its case study: Manish Jain’s $100 domain in a 4.5-lakh-user market, Anupam Mittal’s ten-year wait for venture money. Delayed success is the forge — patience compounds judgment, and judgment is the thing that survives when the market finally arrives.

Practical takeaway — When the timeline slips, ask what the delay is teaching that speed couldn’t. Then write it down — it’s the judgment layer, compounding.

Original: @vaibhavbetter quoting Patrick Bet-David

Briefs · In Passing

Apple’s acquisition wish-list @Jason · 20 Sep
A @johnternus shopping list for the war chest: perplexity_ai (search), WisprFlow (Siri), Superhuman (AI office suite), exolabs (local open-source AI), RobinhoodApp (finance), Hello_GoAI (enterprise), digitalocean (AWS competitor), Disney, DoorDash + Uber (real-world logistics). “Spend that war chest on big swings.”

Bolt Forge @boltdotnew · 14 Sep
Free until 14 Oct: 50× usage on open models (GLM, DeepSeek, Kimi). Opt in and your usage trains a trillion-parameter-class model with arcee_ai. Bolt Lite at $9/month forever, invites close 14 Oct, plus 100 free Pro giveaways. The barbell essay’s free-commodity end, shipped as a product launch.

Self-pity is the worst vice @arnav_kumar · 19 Sep
Worse than pride, ego, or arrogance: self-pity drains agency, chokes confidence, and evaporates talent. “Rage, rage against the dying of the light.” File next to the uncertainty-tolerance story — the “ought” syndrome by another name.

Muse is an A-player colleague @SinaHartung · 15 Sep
Exactly what he’d tell a new hire: Muse set up as an A-player, complete with the SOUL.md persona screenshot — “You’re not a chatbot. You’re becoming someone.” The agent-as-colleague framing, from someone who’s clearly read the manual.

Harry Potter, Bollywood edition @michael56336 · 19 Sep
A collage of some forty parody Harry Potter posters reimagined as modern Indian productions. No thesis, no takeaway — a pure joy break, and this edition’s most delightful save.

Embarrassment is underexplored @NewMentalities · 17 Sep
“Do I deserve this? Am I worthy of this? So irrelevant. Do you want it?” Plus the closer: go out there and make a fool of yourself. The emotional prequel to the ship-fast loop — embarrassment is just the loop’s first turn.