Harshl Kapoor

Student of life 😇

[Fokki @0x_fokki]

I seriously don't understand why schools don't use this yet.

I've been working on the same idea with Claude! A skill that builds everyday machines you can take apart and play with.

Just built a mechanical watch and added it to the site last night. You can wind it, flip it open and watch the little wheel inside tick 8 times a second, 691,200 times a day.

Try it yourself, link in the first reply 👇

[Dr. Brian Hoeflinger, MD @drhoeflinger]

I’m a retired brain surgeon and I wanna tell you why you feel like life is passing by. I just need one minute to explain this to you so hang in there.

Repetitive daily routines stop the brain from recording clear detailed memories. When every day looks the same, your brain does not track time the same as a clock does. It tracks change. If nothing new happens then days, months, and years start to blur together.

This is know as Time compression. When life lacks variety, your brain compresses past days together, making it feel like time is sped up.

To stop feeling like life is passing you by, add new experiences to your life. Break routine habits, like changing your daily home routine, taking a different route to work, or trying a new hobby.

Schedule small trips or plan new adventures so your days do not blend together.

Practice mindfulness by staying fully focused on what you are doing right now and not trying to race off to the next task.

Keep a journal and write down happy memories or memorable parts of the day before you go to sleep.

Take deep, calm breaths when you feel anxious or rushed to return your focus to the moment.

You can and you will retrain your brain to not feel like life is passing you by by following these few simple measures.

[Gergely Orosz @GergelyOrosz]

So many vendors are NOT getting this

I have one or two agents I use and like. For anyone else: give me an MCP interface to connect these agents to so I can use your service

Unless your a frontier AI lab, I prob don't want to use your agent, sorry

[David Sacks @DavidSacks]

This is concerning. For the first time, a Chinese model Kimi K3 has taken #1 on the Frontend Code Arena and is scoring at or near the frontier on other benchmarks.

Meanwhile America is tying itself in knots: politicians and bureaucrats are banning new data centers, piling on state regulations, and pushing for new federal agencies to pre-approve frontier models.

This is how you lose the AI race. The rest of the world won’t play by our rules if we bog ourselves down. Permissionless innovation is how America won the internet and became the technological envy of the world. We can do it again with AI -- while addressing risks in a targeted way -- or we’ll watch our lead evaporate.

[‏ً @omgsidewalks]

I still CANNOT believe humans were gifted a planet full of trees, fruit, water, animals and sunshine and then they invented debt, capitalism and war.

[Robert Greene @RobertGreene]

Do not accept the roles that society foists on you.

Re-create yourself by forging a new identity, one that commands attention and never bores the audience.

Be the master of your own image rather than letting others define if for you. Incorporate dramatic devices into your public gestures and actions – your power will be enhanced and your character will seem larger than life.

[Boris Cherny @bcherny]

As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes:

1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship
2. Builder: quickly turns a prototype/idea into production-grade product/infra
3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance
4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit
5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales

Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS.

A healthy team needs a mix of these, depending on the product:

- A product that is new and pre-PMF needs people that are strong at 1+2+3
- A product that is growing and has found PMF needs 2+3+4 and some 5
- A product that has strong PMF needs 3+4+5 and some 2

Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?

[Patrick Collison @patrickc]

New from Stripe Economics: The Age of the Solopreneur

https://t.co/GTS8jEcK5z

[Naval @naval]

Great products are not so much invented as discovered.

[Anatoli Kopadze @AnatoliKopadze]

https://t.co/eq0oL4fIaR

[Marco @maarcoofdezz]

Dos ingenieros de Anthropic pasaron 24 minutos exponiendo cada función de Claude Code que no sabías que existía y gratis.

La mayoría de las personas pasarán de largo este contenido

[Naval @naval]

Good marketing is finding different ways to tell the truth.

[Aravind Srinivas @AravSrinivas]

Context graphs will be the best way for businesses to enable and deploy agentic harnesses. There's a lot of context fragmentation across so many different tools in every company. A god-mode view that self-improves and self-organizes is the way tacit knowledge can be captured.

[Eric Smith @Eric_Smith08]

A really rich person once told me:

"Money likes water."

It took me years to understand...

[Naval @naval]

The only truly wasted time is time spent wishing you were somewhere else.

[Avi Chawla @_avichawla]

Karpathy said something you'll regret ignoring:

"Remove yourself as the bottleneck. Maximize your leverage. Put in very few tokens, and a huge amount of stuff happens on your behalf."

Loop engineering is the exact thing that does that.

In a hand-run session, the operator handles two things:

- deciding what the agent runs next
- and checking its output before the next step

Both are manual, and both decide how far the agent gets on its own without the operator.

Loop engineering moves both steps into the system.

A core operating structure surrounds the loop, and the diagram below depicts it.

- A schedule decides what to run
- Loop is the maker that produces the work
- A separate checker agent grades the output
- A file on disk holds the state they both read.

The loop runs until either done, max iterations, or an exhausted budget.

Here are some practical engineering considerations:

1) A model grading its own output justifies what it already did instead of catching where it failed.

That's why a separate checker's findings return to the maker as the next instruction. And the cycle repeats until the checker finds nothing left to fix.

2) A loop with no stop condition burns tokens, and the cost climbs fast once sub-agents and long runs add up.

That's why the exit must be set before the loop runs, not while it is running.

A simple exit could be:
↳ fix only the major issues, run one final pass, and stop after two loops, with "all tests pass and lint clean" as the rule that ends it.

3) State has to live on disk, not in context.

The model forgets everything between runs, so an MD file or a knowledge graph holds what is done and what is still open.

Each run reads it and writes back to it, which lets a loop pick up again after days.

4) The lower the verification bar, the safer the loop.

Boring, repetitive checks like a stale version string or a missing test are trivial to verify, so a loop runs them with little risk while the operator is away.

Judgment-heavy work is loopable too, but only as far as the checker can confirm the result.

Let's look at how an unattended loop fails in two ways.

1) It reports done when nothing is actually verified.

The separate checker exists to prevent it, but it merges code faster than anyone reads it, so over weeks, the team stops understanding its own codebase while every check stays green.

Green tests say the code passed the tests, not that anyone knows what shipped. Someone still has to read what the loop merges.

2) The checker keeps a running loop honest, but it only catches failures inside a run.

The harness around the loop, like the prompts, tools, and checks wrapped around the model, still drifts and breaks in production as models change.

That repair loop is usually run by hand based on observability traces.

My co-founder wrote a detailed walkthrough (with code) on making that harness repair itself, where a failing trace gets diagnosed, the fix is verified against the exact input that failed, and the failure is locked as a regression test so it cannot recur.

Read it below.

[Shreyas Doshi @shreyas]

This recent @bchesky podcast with @patrick_oshag belongs to the hall of fame of tech podcast episodes. Very likely the deepest founder conversation after the Steve Jobs lost interview in the 90s.

Currently it has 90k views; it deserves 100X more views.

https://t.co/o9rzq0ZXuS

[Kate Deyneka @katedeyneka]

best accounts to follow from each frontier lab to stay constantly up to date

Anthropic
@karpathy - must-follow account for AI; recently joined Anthropic
@bcherny - Claude Code creator, always shares great tips
@trq212 - also a Claude Code developer; writes amazing articles on CC

OpenAI
@polynoamial - works on reasoning research, shares a lot of technical details
@gabriel1 - Sora developer, great career path
@jxnlco - works on dev experience, shares a lot about Codex

Google AI
@OfficialLoganK - all the major Google Gemini and AI Studio updates
@ammaar - product and design; shares great things about vibe-coding in Google AI Studio
@fofrAI - cool use cases for generative models

Cursor
@leerob - the loudest voice behind Cursor updates
@ericzakariasson - shares great insights on using Cursor
@mntruell - Cursor’s CEO; major releases and usage updates

xAI
@milichab - recently joined xAI, shares updates on Grok
@skcd42 - also covers major Grok releases
@elonmusk - Elon does a great job reposting and hyping all xAI products

who else did I miss?

[David Senra @davidsenra]

This conversation with @RickRubin is special. Here's a 2 minute preview that I’ve watched 15 times.

The episode will be out tomorrow:

[DAN KOE @thedankoe]

The most important decision of your life