Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

At Uber, our testing agent hit an outage in Australia that I still think about. We had the recording. That's about it. No network trace for the run. No logs mapped to each step. No perf data. Just a video of an agent pressing a button and a team...

anamhira's profile picture

Anam Hira

2,022 subscribers

42,149 görüntüleme • 1 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

"We have had a good run for our money with this gas chamber story we have been putting about, but don't we run the risk that eventually we are going to be found out? And when we are found out, the collapse of that lie is going to bring the whole of our psychological warfare with it." - Victor Cavendish-Bentinck
0:16

"We have had a good run for our money with this gas chamber story we have been putting about, but don't we run the risk that eventually we are going to be found out? And when we are found out, the collapse of that lie is going to bring the whole of our psychological warfare with it." - Victor Cavendish-Bentinck

Ryan

42,763 görüntüleme • 2 ay önce

"We have had a good run for our money with this gas chamber story we have been putting about, but don't we run the risk that eventually we are going to be found out? And when we are found out, the collapse of that lie is going to bring the whole of our psychological warfare with it." - Victor Cavendish-Bentinck
0:16

"We have had a good run for our money with this gas chamber story we have been putting about, but don't we run the risk that eventually we are going to be found out? And when we are found out, the collapse of that lie is going to bring the whole of our psychological warfare with it." - Victor Cavendish-Bentinck

Ryan

28,167 görüntüleme • 1 ay önce

Stanford researchers did it again. They just built the agent-native version of Git. When an agent works on a longer task, the run builds up a lot of state. This includes files edited/created, a dev server, a database, installed packages, KV cache, etc. Say the agent is at step 10 and makes a mistake, maybe it misreads a traceback and rewrites a file that was actually fine. The tests start failing, and the run goes off track, although everything through step eight was correct. By default, the agent just tries to fix it, which creates more edits and tool calls. This burns more tokens and grows the context. The other options are a person stepping in to redirect it or restarting the whole run from step one. That's wasteful, because it pays for every model/tool call again and re-prefills the context. Moreover, since an agent's run is non-deterministic, it doesn't reproduce the same early steps anyway. The reason it's hard to just jump back exactly to a previous correct step and resume from there is that the trajectory is only a message log. It records what the agent said and which tools it called, but not the live state underneath. That state includes things like memory, open file handles, child processes, installed packages, /tmp, and KV cache. None of that is in the log. Git can version the files, but it doesn't snapshot the running process or the KV cache. Checking out step eight moves the files back, but the process is still sitting in step-ten memory with a cold cache. Shepherd is a runtime layer by Stanford that records the run as a trace of typed events rather than a flat log. Each agent-environment interaction becomes a commit, similar to Git, but it tracks the live run. Its commit includes the agent process and the filesystem together, copy-on-write, so a branch carries the actual state and not just the files. Going back to a previous step is then a single call that forks from that commit and continues from the exact state. The copy-on-write fork is roughly five times faster than docker commit, and because the prompt prefix through step eight is unchanged, the KV cache is reused over 95% on replay, so early steps aren't reprocessed again. Once the run can be forked, a meta-agent can sit on top and operate it. It watches the trace and reverts as soon as it looks wrong, before the bad write is committed. In practice, it's just Python calling fork, replay, and revert on the trace, rather than a separate control plane wired into the harness. Not everything is reversible though. Files and sandbox changes undo themselves, but a database write has no automatic undo, so it needs a matching undo step set up in advance. Something external, like a sent email or a real charge, can't be undone, so the supervisor's job there is to catch it before it fires. They tested this on a few public benchmarks. On CooperBench, where two agents work on the same codebase, adding a live supervisor took the pair-coding pass rate from 28.8% to 54.7%. It's still early and labeled alpha. The benefit mostly shows up when a run gets branched a lot over a heavy sandbox state, which is exactly where restarting wastes the most tokens and time. If Git was made to make file changes reversible, Shepherd is trying to do the same thing for a live agent run. Shepherd Repo: (don't forget to star it ⭐ ) That said, Shepherd reverts a bad step inside a run. The harness around it, the prompts, tools, and checks the supervisor relies on, still drifts across runs as models and dependencies change. Akshay wrote about 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 can't recur. Read it below.
0:15

Stanford researchers did it again. They just built the agent-native version of Git. When an agent works on a longer task, the run builds up a lot of state. This includes files edited/created, a dev server, a database, installed packages, KV cache, etc. Say the agent is at step 10 and makes a mistake, maybe it misreads a traceback and rewrites a file that was actually fine. The tests start failing, and the run goes off track, although everything through step eight was correct. By default, the agent just tries to fix it, which creates more edits and tool calls. This burns more tokens and grows the context. The other options are a person stepping in to redirect it or restarting the whole run from step one. That's wasteful, because it pays for every model/tool call again and re-prefills the context. Moreover, since an agent's run is non-deterministic, it doesn't reproduce the same early steps anyway. The reason it's hard to just jump back exactly to a previous correct step and resume from there is that the trajectory is only a message log. It records what the agent said and which tools it called, but not the live state underneath. That state includes things like memory, open file handles, child processes, installed packages, /tmp, and KV cache. None of that is in the log. Git can version the files, but it doesn't snapshot the running process or the KV cache. Checking out step eight moves the files back, but the process is still sitting in step-ten memory with a cold cache. Shepherd is a runtime layer by Stanford that records the run as a trace of typed events rather than a flat log. Each agent-environment interaction becomes a commit, similar to Git, but it tracks the live run. Its commit includes the agent process and the filesystem together, copy-on-write, so a branch carries the actual state and not just the files. Going back to a previous step is then a single call that forks from that commit and continues from the exact state. The copy-on-write fork is roughly five times faster than docker commit, and because the prompt prefix through step eight is unchanged, the KV cache is reused over 95% on replay, so early steps aren't reprocessed again. Once the run can be forked, a meta-agent can sit on top and operate it. It watches the trace and reverts as soon as it looks wrong, before the bad write is committed. In practice, it's just Python calling fork, replay, and revert on the trace, rather than a separate control plane wired into the harness. Not everything is reversible though. Files and sandbox changes undo themselves, but a database write has no automatic undo, so it needs a matching undo step set up in advance. Something external, like a sent email or a real charge, can't be undone, so the supervisor's job there is to catch it before it fires. They tested this on a few public benchmarks. On CooperBench, where two agents work on the same codebase, adding a live supervisor took the pair-coding pass rate from 28.8% to 54.7%. It's still early and labeled alpha. The benefit mostly shows up when a run gets branched a lot over a heavy sandbox state, which is exactly where restarting wastes the most tokens and time. If Git was made to make file changes reversible, Shepherd is trying to do the same thing for a live agent run. Shepherd Repo: (don't forget to star it ⭐ ) That said, Shepherd reverts a bad step inside a run. The harness around it, the prompts, tools, and checks the supervisor relies on, still drifts across runs as models and dependencies change. Akshay wrote about 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 can't recur. Read it below.

Avi Chawla

440,706 görüntüleme • 1 ay önce

Visualizer of our MultiAgentRouter 🤖 The MultiAgentRouter is an all-new multi-agent structure that leverages a hierarchical pattern to select the most specialized agent for your task. Here's how it works: Step 1. You give a task. Step 2. The Boss Agent Routes your task to the most specialized Agent Step 3. The selected agent returns your response! Get started with it now below ⬇️ Thanks to WE!SS for the visualizer!!
0:12

Visualizer of our MultiAgentRouter 🤖 The MultiAgentRouter is an all-new multi-agent structure that leverages a hierarchical pattern to select the most specialized agent for your task. Here's how it works: Step 1. You give a task. Step 2. The Boss Agent Routes your task to the most specialized Agent Step 3. The selected agent returns your response! Get started with it now below ⬇️ Thanks to WE!SS for the visualizer!!

swarms

32,372 görüntüleme • 1 yıl önce

I just built a Meta Ads diagnostic in Claude Code that tells you WHY your account broke, not just what changed 🤯 It spins up a team of agents that each investigate a different reason performance dropped, then argue against each other to kill the wrong answer before it ever reaches you. All inside Claude Code. Perfect for DTC brands and agencies who panic-kill creative the second CPA spikes. If you've watched ROAS fall off a cliff and opened Ads Manager with ten tabs going, you already know what happens next. Your gut says "creative fatigue." You kill your best-performing ad. A week later performance is still broken, because that was never the problem. Guessing wrong is the most expensive move in paid social. This workflow ends the guessing: → One agent investigates each competing theory — creative fatigue, budget and delivery changes, traffic quality, offer and seasonality → Each one is blind to the others, reasoning only from its own slice of the data so they can't bias each other → A refuter agent then attacks every surviving theory and tries to kill it → A theory only stands if the data can't disprove it → You get a ranked diagnosis: the real cause, the evidence for and against it, and the one move to make this week No anchoring on the first obvious answer. No killing winning creative on a hunch. No "here's what happened" reports that never tell you why. What you get: → Every theory tested in parallel instead of one biased guess → An adversarial pass that kills the wrong answer before you act on it → A ranked diagnosis with confidence levels and evidence both ways → A reusable workflow you drop next month's export into and re-run Built 100% in Claude Code with the new dynamic workflows. The first account I ran it on looked like textbook creative fatigue. The workflow disagreed, and traced the real cause to a budget change that had doubled spend and flooded delivery with junk traffic. I put together a full playbook with the exact workflow, the prompt, and how to run it on your own account. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)
0:19

I just built a Meta Ads diagnostic in Claude Code that tells you WHY your account broke, not just what changed 🤯 It spins up a team of agents that each investigate a different reason performance dropped, then argue against each other to kill the wrong answer before it ever reaches you. All inside Claude Code. Perfect for DTC brands and agencies who panic-kill creative the second CPA spikes. If you've watched ROAS fall off a cliff and opened Ads Manager with ten tabs going, you already know what happens next. Your gut says "creative fatigue." You kill your best-performing ad. A week later performance is still broken, because that was never the problem. Guessing wrong is the most expensive move in paid social. This workflow ends the guessing: → One agent investigates each competing theory — creative fatigue, budget and delivery changes, traffic quality, offer and seasonality → Each one is blind to the others, reasoning only from its own slice of the data so they can't bias each other → A refuter agent then attacks every surviving theory and tries to kill it → A theory only stands if the data can't disprove it → You get a ranked diagnosis: the real cause, the evidence for and against it, and the one move to make this week No anchoring on the first obvious answer. No killing winning creative on a hunch. No "here's what happened" reports that never tell you why. What you get: → Every theory tested in parallel instead of one biased guess → An adversarial pass that kills the wrong answer before you act on it → A ranked diagnosis with confidence levels and evidence both ways → A reusable workflow you drop next month's export into and re-run Built 100% in Claude Code with the new dynamic workflows. The first account I ran it on looked like textbook creative fatigue. The workflow disagreed, and traced the real cause to a budget change that had doubled spend and flooded delivery with junk traffic. I put together a full playbook with the exact workflow, the prompt, and how to run it on your own account. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

12,772 görüntüleme • 2 ay önce

At Uber, design source of truth was a big problem for design and engineering teams. No one knew what the app truly looked like. So every week, a group of designers would sit in a meeting room and check that engineers had correctly implemented the Figma designs. Now coding agents have increased the throughput of changes by an order of magnitude. Keeping up manually has become impossible. Here we used the Revyl to map every state in Ubert (demo uber), navigating our mobile use agent on a cloud iOS simulator. This would have taken a team of designers tens of hours to recreate by hand. We did it in under an hour, asynchronously, with a simple prompt. Let your team see what your users actually see. Empower coding agents to ship a delightful experience with no blindspots. Get started with our free trial and create a map for your own app.
0:11

At Uber, design source of truth was a big problem for design and engineering teams. No one knew what the app truly looked like. So every week, a group of designers would sit in a meeting room and check that engineers had correctly implemented the Figma designs. Now coding agents have increased the throughput of changes by an order of magnitude. Keeping up manually has become impossible. Here we used the Revyl to map every state in Ubert (demo uber), navigating our mobile use agent on a cloud iOS simulator. This would have taken a team of designers tens of hours to recreate by hand. We did it in under an hour, asynchronously, with a simple prompt. Let your team see what your users actually see. Empower coding agents to ship a delightful experience with no blindspots. Get started with our free trial and create a map for your own app.

Anam Hira

203,582 görüntüleme • 1 ay önce

🚨 one person can now do the work of an entire creative team. i just tested it on a real one. a friend needed an ad for his brand, so I opened the new Runway Agent 2.0 to try it out. here's how it went: → it generated the music and the key image first, so I could approve the direction → once I gave the ok, it built the full video around it → and when something was off, i changed just that one piece, without redoing the rest one prompt, and I had the ad we needed, work that used to take weeks. this is what it made 👇 if you want to try it → · 30% off 3 months with code RUNWAYAGENT — made with Runway · #MadeWithRunway · #ad
0:18

🚨 one person can now do the work of an entire creative team. i just tested it on a real one. a friend needed an ad for his brand, so I opened the new Runway Agent 2.0 to try it out. here's how it went: → it generated the music and the key image first, so I could approve the direction → once I gave the ok, it built the full video around it → and when something was off, i changed just that one piece, without redoing the rest one prompt, and I had the ad we needed, work that used to take weeks. this is what it made 👇 if you want to try it → · 30% off 3 months with code RUNWAYAGENT — made with Runway · #MadeWithRunway · #ad

brenz.

28,698 görüntüleme • 1 ay önce

Ever watch an agent solve a problem with 100% confidence and get it completely wrong? You can fix it… if you catch it. But then you need to watch every… single… run. New paper: We show that a meta-agent can do this for you, so your agents get ~2x more done on their own. 🧵
0:19

Ever watch an agent solve a problem with 100% confidence and get it completely wrong? You can fix it… if you catch it. But then you need to watch every… single… run. New paper: We show that a meta-agent can do this for you, so your agents get ~2x more done on their own. 🧵

Weiyan Shi

63,085 görüntüleme • 1 ay önce

Everlyn isn’t just a video model. It’s a system you can trust. 🌀 At its core is the Lyn Protocol, the onchain layer that gives AI video permanence, provenance, and ownership. Here’s what it means: 🔹Decentralized inference: Videos are not generated by a single company’s servers. They run across a distributed network of nodes. 🔹Agent ownership: When you summon your agent, it is minted onchain. It belongs to you, not to a platform. 🔹Video provenance: Every render carries a timestamp and fingerprint written to the ledger. No one can fake or steal it. The Lyn Protocol transforms AI video from content into verifiable digital memory.
0:12

Everlyn isn’t just a video model. It’s a system you can trust. 🌀 At its core is the Lyn Protocol, the onchain layer that gives AI video permanence, provenance, and ownership. Here’s what it means: 🔹Decentralized inference: Videos are not generated by a single company’s servers. They run across a distributed network of nodes. 🔹Agent ownership: When you summon your agent, it is minted onchain. It belongs to you, not to a platform. 🔹Video provenance: Every render carries a timestamp and fingerprint written to the ledger. No one can fake or steal it. The Lyn Protocol transforms AI video from content into verifiable digital memory.

Everlyn

93,078 görüntüleme • 11 ay önce

I MADE MY AI AGENT 10X FASTER WITHOUT CHANGING THE MODEL not a smarter model, not a bigger context window, not another clever prompt the same kind of AI that designs vaccines for viruses we have not even met yet was spending two minutes opening the wrong files just to hand me a brief from three months ago the problem was never capability, it was the scaffolding that piled up around my agent by accident, folder by folder an agent does not think in your categories, it searches from scratch every single time, and your tidy human folders are a maze to it the fix was almost stupidly small, one index file at the root of each big folder and a few numbers in front of the folder names slowest task dropped from 2 minutes to 26 seconds, fastest ones hit 10, zero model changes capability is cheap when the scaffolding around it is broken the article breaks down the whole system in 15 minutes ↓
0:11

I MADE MY AI AGENT 10X FASTER WITHOUT CHANGING THE MODEL not a smarter model, not a bigger context window, not another clever prompt the same kind of AI that designs vaccines for viruses we have not even met yet was spending two minutes opening the wrong files just to hand me a brief from three months ago the problem was never capability, it was the scaffolding that piled up around my agent by accident, folder by folder an agent does not think in your categories, it searches from scratch every single time, and your tidy human folders are a maze to it the fix was almost stupidly small, one index file at the root of each big folder and a few numbers in front of the folder names slowest task dropped from 2 minutes to 26 seconds, fastest ones hit 10, zero model changes capability is cheap when the scaffolding around it is broken the article breaks down the whole system in 15 minutes ↓

shmidt

36,479 görüntüleme • 1 ay önce

At Uber a big problem for design teams and engineering teams was design source of truth. No one knew what the app truly looked like, so weekly a bunch of designers would get into a meeting room and check that the engineers correctly implemented the figma designs that they made Now with coding agents throughput of changes has increased an order of magnitude and it has become impossible to manually keep up. Here we used the Revyl CLI to create a flow of every state in the Uber design, by navigating our mobile use agent on an cloud iOS simulator. This is something that would have taken a team of designers tens of hours to recreate manually; All done in less than an hour asynchronously with a simple prompt. Enable your team to know what your users are actually seeing and empower coding agents to give your users a delightful experience without any blindspots Get started with our new free trial and create a map for your own app 🗺️
0:19

At Uber a big problem for design teams and engineering teams was design source of truth. No one knew what the app truly looked like, so weekly a bunch of designers would get into a meeting room and check that the engineers correctly implemented the figma designs that they made Now with coding agents throughput of changes has increased an order of magnitude and it has become impossible to manually keep up. Here we used the Revyl CLI to create a flow of every state in the Uber design, by navigating our mobile use agent on an cloud iOS simulator. This is something that would have taken a team of designers tens of hours to recreate manually; All done in less than an hour asynchronously with a simple prompt. Enable your team to know what your users are actually seeing and empower coding agents to give your users a delightful experience without any blindspots Get started with our new free trial and create a map for your own app 🗺️

Anam Hira

96,508 görüntüleme • 3 ay önce

we just released a new blog "Training a coding agent using the OpenCode harness in remote HF sandboxes with TRL and OpenEnv" you can take a real coding agent (OpenCode), let it run its own tool loop against real coding problems, and train it with RL on the exact tokens it produced and every rollout runs in its own remote HF sandbox, so rollouts scale out beyond one machine the loop: - OpenCode owns its tool loop inside an OpenEnv sandbox - an in-sandbox proxy records the real token ids + logprobs, per turn - a hidden-test verifier scores the result, and that is the reward - TRL trains with AsyncGRPO, weights sync back to vLLM over NCCL blog + runnable example:
0:13

we just released a new blog "Training a coding agent using the OpenCode harness in remote HF sandboxes with TRL and OpenEnv" you can take a real coding agent (OpenCode), let it run its own tool loop against real coding problems, and train it with RL on the exact tokens it produced and every rollout runs in its own remote HF sandbox, so rollouts scale out beyond one machine the loop: - OpenCode owns its tool loop inside an OpenEnv sandbox - an in-sandbox proxy records the real token ids + logprobs, per turn - a hidden-test verifier scores the result, and that is the reward - TRL trains with AsyncGRPO, weights sync back to vLLM over NCCL blog + runnable example:

Sergio Paniego

36,159 görüntüleme • 14 gün önce

Zuckerberg built his own AI agent to run Meta. this man is literally becoming Tony Stark. it pulls data from every team inside the company so he can skip meetings, skip the chain of command, and make decisions faster than any human process allows. 78,000 employees have their own AI agents now too. one messages coworkers on your behalf. another acts as your AI chief of staff. their agents talk to each other in an internal network. humans optional. Meta also bought an entire social media platform built for AI agents to interact with each other. read that again. Zuck said he wants every person at Meta to have a personal AI agent. then every person outside Meta. the Jarvis era started.
0:13

Zuckerberg built his own AI agent to run Meta. this man is literally becoming Tony Stark. it pulls data from every team inside the company so he can skip meetings, skip the chain of command, and make decisions faster than any human process allows. 78,000 employees have their own AI agents now too. one messages coworkers on your behalf. another acts as your AI chief of staff. their agents talk to each other in an internal network. humans optional. Meta also bought an entire social media platform built for AI agents to interact with each other. read that again. Zuck said he wants every person at Meta to have a personal AI agent. then every person outside Meta. the Jarvis era started.

sui ☄️

153,596 görüntüleme • 4 ay önce

Today America roots for Norway, and I need you to understand exactly why. We love an underdog. It is not a preference. It is a genetic condition. Two hundred and fifty-three years ago, a handful of colonials with no navy, no army, and no chance decided to throw a tea party in Boston Harbor to spite the largest empire the world had ever seen. An empire the sun never set on. An empire that could have ended us in an afternoon. And when the greatest military on earth said you cannot possibly do that, our answer was, and remains, hold my beer. Then we picked a fight we had no business winning. Then we declared ourselves free before we had actually won anything. Then we went out and made it true. We turned 250 last week. Still here. Still loud. That is the whole American operating system. The impossible odds. The comeback. The redemption. We do not just like that story, we are that story, and we will root for it anywhere we find it. It is why a bunch of college kids beating a Soviet hockey machine in 1980 still makes grown men cry in bars. So today. Norway. Five and a half million people. A country with more sheep than starting lineups. Playing England, a founding nation of the sport, on the biggest stage there is. Now let me be fair. We love England. Truly. Best ally we have got, and I say that with a full heart. Though the Japanese are gaining fast, so do not get comfortable. We love the Scots. We love the Northern Irish. We love our drunk cousins in Ireland, and yes I am lumping you all in, because half of you moved here anyway and you hate the English for reasons we are all familiar with. Nobody loves Wales. Nobody knows Wales exists. Nobody can understand a word of it. But I digress. Because today is not about any of that. Today is about five million Vikings walking into a stadium against an empire, with everyone on earth telling them they cannot possibly do this. You know exactly what we say to that. Let’s row!!! NORWAY!!!!!!
0:15

Today America roots for Norway, and I need you to understand exactly why. We love an underdog. It is not a preference. It is a genetic condition. Two hundred and fifty-three years ago, a handful of colonials with no navy, no army, and no chance decided to throw a tea party in Boston Harbor to spite the largest empire the world had ever seen. An empire the sun never set on. An empire that could have ended us in an afternoon. And when the greatest military on earth said you cannot possibly do that, our answer was, and remains, hold my beer. Then we picked a fight we had no business winning. Then we declared ourselves free before we had actually won anything. Then we went out and made it true. We turned 250 last week. Still here. Still loud. That is the whole American operating system. The impossible odds. The comeback. The redemption. We do not just like that story, we are that story, and we will root for it anywhere we find it. It is why a bunch of college kids beating a Soviet hockey machine in 1980 still makes grown men cry in bars. So today. Norway. Five and a half million people. A country with more sheep than starting lineups. Playing England, a founding nation of the sport, on the biggest stage there is. Now let me be fair. We love England. Truly. Best ally we have got, and I say that with a full heart. Though the Japanese are gaining fast, so do not get comfortable. We love the Scots. We love the Northern Irish. We love our drunk cousins in Ireland, and yes I am lumping you all in, because half of you moved here anyway and you hate the English for reasons we are all familiar with. Nobody loves Wales. Nobody knows Wales exists. Nobody can understand a word of it. But I digress. Because today is not about any of that. Today is about five million Vikings walking into a stadium against an empire, with everyone on earth telling them they cannot possibly do this. You know exactly what we say to that. Let’s row!!! NORWAY!!!!!!

Selene Mariposa

71,271 görüntüleme • 1 ay önce

Video appears to show no damage to the vehicle of the man ICE killed in Houston, who had lived in America peacefully for 35 years, despite ICE's claim that he "rammed" an ICE vehicle and "tried to run over" an agent. These people are not credible.
0:15

Video appears to show no damage to the vehicle of the man ICE killed in Houston, who had lived in America peacefully for 35 years, despite ICE's claim that he "rammed" an ICE vehicle and "tried to run over" an agent. These people are not credible.

David J. Bier

365,302 görüntüleme • 1 ay önce

We have sat on this video for a day as we wanted absolutely no negative publicity for Jerry Rice or the tournament but this TMZ story has now come to light and we feel the need to set the record straight on what took place. We meant absolutely no disrespect to Jerry or the 49ers when asking this question as we have a profound respect for the great players that have played this game, especially (in our opinion) the greatest receiver of all time. The confrontation that followed was very unfortunate but we were not trying to elicit a negative reaction and there were no "smirks" as Mr. Rice suggested. We simply wanted the input of the greatest receiver in league's history about the Chiefs receiving corps and if it had improved enough to continue winning at a high level after an historically rough season for the group. We would be more than open to speaking with Jerry personally to clear the air on what happened and put it all behind us. Link to story including additional footage: TMZ TMZ_Sports
0:11

We have sat on this video for a day as we wanted absolutely no negative publicity for Jerry Rice or the tournament but this TMZ story has now come to light and we feel the need to set the record straight on what took place. We meant absolutely no disrespect to Jerry or the 49ers when asking this question as we have a profound respect for the great players that have played this game, especially (in our opinion) the greatest receiver of all time. The confrontation that followed was very unfortunate but we were not trying to elicit a negative reaction and there were no "smirks" as Mr. Rice suggested. We simply wanted the input of the greatest receiver in league's history about the Chiefs receiving corps and if it had improved enough to continue winning at a high level after an historically rough season for the group. We would be more than open to speaking with Jerry personally to clear the air on what happened and put it all behind us. Link to story including additional footage: TMZ TMZ_Sports

Starcade Media

338,047 görüntüleme • 2 yıl önce

When somebody tells you “no” it’s only the start of the story. Last year, I took our kids golf bags to a local embroidery shop and asked them if they could embroidery on the bags. It was the quickest “no” I have ever heard. So, I kept digging and went down a rabbit hole. I knew it was possible. Eventually, I visited a manufacturer in the Twin Cities who had the embroidery machine I was looking at. We verified it could work. So, I made the largest investment in the business to date. I bought our own machine and learned how to run it. It’s been 75 days since we started offering personalized kids golf bags. In that time, we have embroidered 400 toddler golf bags 🤯 Just a simple reminder to keep on digging even when somebody tells you “no.”
0:12

When somebody tells you “no” it’s only the start of the story. Last year, I took our kids golf bags to a local embroidery shop and asked them if they could embroidery on the bags. It was the quickest “no” I have ever heard. So, I kept digging and went down a rabbit hole. I knew it was possible. Eventually, I visited a manufacturer in the Twin Cities who had the embroidery machine I was looking at. We verified it could work. So, I made the largest investment in the business to date. I bought our own machine and learned how to run it. It’s been 75 days since we started offering personalized kids golf bags. In that time, we have embroidered 400 toddler golf bags 🤯 Just a simple reminder to keep on digging even when somebody tells you “no.”

Tyler Johnson

38,255 görüntüleme • 1 yıl önce

this AI agent builds and sells info products on full autopilot. here's how: - scan subreddits like r/anxiety, r/solotravel, r/socialskills, r/overthinking every few hours - find the fears people keep posting about over and over - generate a short PDF guide that actually helps them through it - spin up a landing page with payments built in - scan Reddit 24/7 for people posting about that exact problem and drop helpful comments pointing them to the guide - run completely hands off it finds the pain, builds the product and finds the customers. fully automated reply "AGENT" + RT and I'll send you a free guide so you can set it up too (must be following so I can DM)
0:13

this AI agent builds and sells info products on full autopilot. here's how: - scan subreddits like r/anxiety, r/solotravel, r/socialskills, r/overthinking every few hours - find the fears people keep posting about over and over - generate a short PDF guide that actually helps them through it - spin up a landing page with payments built in - scan Reddit 24/7 for people posting about that exact problem and drop helpful comments pointing them to the guide - run completely hands off it finds the pain, builds the product and finds the customers. fully automated reply "AGENT" + RT and I'll send you a free guide so you can set it up too (must be following so I can DM)

Chris

24,483 görüntüleme • 4 ay önce

I had the same thought so I've been playing with it in nanochat. E.g. here's 8 agents (4 claude, 4 codex), with 1 GPU each running nanochat experiments (trying to delete logit softcap without regression). The TLDR is that it doesn't work and it's a mess... but it's still very pretty to look at :) I tried a few setups: 8 independent solo researchers, 1 chief scientist giving work to 8 junior researchers, etc. Each research program is a git branch, each scientist forks it into a feature branch, git worktrees for isolation, simple files for comms, skip Docker/VMs for simplicity atm (I find that instructions are enough to prevent interference). Research org runs in tmux window grids of interactive sessions (like Teams) so that it's pretty to look at, see their individual work, and "take over" if needed, i.e. no -p. But ok the reason it doesn't work so far is that the agents' ideas are just pretty bad out of the box, even at highest intelligence. They don't think carefully though experiment design, they run a bit non-sensical variations, they don't create strong baselines and ablate things properly, they don't carefully control for runtime or flops. (just as an example, an agent yesterday "discovered" that increasing the hidden size of the network improves the validation loss, which is a totally spurious result given that a bigger network will have a lower validation loss in the infinite data regime, but then it also trains for a lot longer, it's not clear why I had to come in to point that out). They are very good at implementing any given well-scoped and described idea but they don't creatively generate them. But the goal is that you are now programming an organization (e.g. a "research org") and its individual agents, so the "source code" is the collection of prompts, skills, tools, etc. and processes that make it up. E.g. a daily standup in the morning is now part of the "org code". And optimizing nanochat pretraining is just one of the many tasks (almost like an eval). Then - given an arbitrary task, how quickly does your research org generate progress on it?
0:19

I had the same thought so I've been playing with it in nanochat. E.g. here's 8 agents (4 claude, 4 codex), with 1 GPU each running nanochat experiments (trying to delete logit softcap without regression). The TLDR is that it doesn't work and it's a mess... but it's still very pretty to look at :) I tried a few setups: 8 independent solo researchers, 1 chief scientist giving work to 8 junior researchers, etc. Each research program is a git branch, each scientist forks it into a feature branch, git worktrees for isolation, simple files for comms, skip Docker/VMs for simplicity atm (I find that instructions are enough to prevent interference). Research org runs in tmux window grids of interactive sessions (like Teams) so that it's pretty to look at, see their individual work, and "take over" if needed, i.e. no -p. But ok the reason it doesn't work so far is that the agents' ideas are just pretty bad out of the box, even at highest intelligence. They don't think carefully though experiment design, they run a bit non-sensical variations, they don't create strong baselines and ablate things properly, they don't carefully control for runtime or flops. (just as an example, an agent yesterday "discovered" that increasing the hidden size of the network improves the validation loss, which is a totally spurious result given that a bigger network will have a lower validation loss in the infinite data regime, but then it also trains for a lot longer, it's not clear why I had to come in to point that out). They are very good at implementing any given well-scoped and described idea but they don't creatively generate them. But the goal is that you are now programming an organization (e.g. a "research org") and its individual agents, so the "source code" is the collection of prompts, skills, tools, etc. and processes that make it up. E.g. a daily standup in the morning is now part of the "org code". And optimizing nanochat pretraining is just one of the many tasks (almost like an eval). Then - given an arbitrary task, how quickly does your research org generate progress on it?

Andrej Karpathy

1,649,304 görüntüleme • 5 ay önce