Method · BodyA locally coherent in-season lifting template: lower body day one pairs a squat pattern supersetted with a jump, plus a knee-dominant hamstring exercise (Nordic or Razor Curl) supersetted with a 3D lunge attacking the groin (lateral lunge), and optional mobility or core work. Upper body day one uses a horizontal push (dumbbell bench, push-up, floor press) supersetted with a dynamic horizontal push (band push-up or med ball throw), an upper back movement (face pull, band pull apart, YTWs) supersetted with a vertical pull (chin-up, pull-down), and optional grip work. The second lower body day uses a split squat pattern or trap bar deadlift per athlete preference — chosen based on age, injury history, and testing profile — supersetted with a split squat jump, then hip-dominant posterior chain
Consequential creator advice requires independent verification before Today can promote it.
Method, not a verified protocol.
Garage Strength · How The Best Pro Baseball Players Actually Train w/ MLB Strength Coach Stephanie Grubbs
RecommendationThe guest endorses creating something like the NTSB for AI, emphasizing that the key to aviation-style oversight is independence (the NTSB was set up as an independent agency in 1967), and that non-punitive reporting systems like ASRS incentivized manufacturers and airlines to share safety information and take every accident seriously.
Y Combinator · AI Safety Fact vs. Fiction | YC Paper Club
RecommendationCJ calls visibility into what the agent is doing table stakes: maintain a durable event stream with full trajectory across the entire lifecycle, listen to it in real time, and immediately interrupt any sessions going in a direction you don't like. You can also build a custom UI on top of the event stream to show tool calls and messages, and when accessing a flow programmatically you see every tool call, result, and sub-agent handoff.
AI Engineer · Why One AI Agent Isn’t Enough (And How to Run 1,000) - CJ Avilla & Harrison Stall, Anthropic
AnecdoteWhen kicking off a big multi-agent project, the speaker wrote a short high-level prompt ('Ken Thompson made Unix in a week. Can you try and make an operating system...') and let the agents run rather than over-specifying; gave it a GitHub repo so output is inspectable and versioned; asked it to have a team of docs writers writing documentation about what each phase implemented so progress is monitorable via the repo; and instructed the flow to use a specific model for documentation writing ('use Sonnet 5.5').
AI Engineer · Why One AI Agent Isn’t Enough (And How to Run 1,000) - CJ Avilla & Harrison Stall, Anthropic
RecommendationJed recommends switching the permission policy from 'always ask' to auto mode as the easiest, lowest-hanging fruit for Cloud Managed Agents integrations, letting Claude determine whether a single tool call is safe or destructive before acting.
Contested by David Pawlan on The a16z Show
Also discussed by Thariq Shihipar on Latent.Space (unclassified source — not counted until classified). Not counted as independent sources.
AI Engineer · Why One AI Agent Isn’t Enough (And How to Run 1,000) - CJ Avilla & Harrison Stall, Anthropic
MethodLeash designs DEL libraries from 2–3 building blocks stitched together, considering shapes like forked (Y-shaped), linear, and macrocyclic geometries. Practical constraints shape the design: where the DNA tag goes and how that causes problems, commercial availability of building blocks (preferred over custom synthesis when speed matters, since custom synthesis takes longer), and the chemistry required to stitch them together. A chemical library built a certain way will be good for some protein target classes and bad for others, so plan which corners of protein space you're optimizing for. A known failure mode: fine-grained SAR mapping (e.g., moving a nitrogen around every position of a ring) is highly desirable but usually unavailable commercially. Quigley is not too worried about easy-asy
described as Leash's design practice
Method, not a verified protocol.
Latent.Space · Lab-in-the-Loop at Compute Speed — Ian Quigley, Leash Bio
MethodAfter basic concepts, Leash gives the model 10 binders and 10 close non-binders and asks it to explain why the binders bind. The model is then given a catalog of millions of molecules from which it picks 5-10 to test its binding hypothesis, gets answers back instantly like a coding sandbox, and updates its hypothesis. The goal is to find the best binder in as few steps as possible, like a medicinal chemist would.
Method, not a verified protocol.
Latent.Space · Lab-in-the-Loop at Compute Speed — Ian Quigley, Leash Bio
Recommendation · MoneyRandy Hunt recommends building design teams where designers are highly technical and ship code in the production application — a 'software design team.' He says it's hard for him to imagine building a software product any other way, and he built such a team at Etsy in 2010, long before coding agents made it trendy.
Design Better · Randy Hunt: Notion and Etsy design leader on why the best design teams stay small
Recommendation · MoneyOne of Replit's actual shipped fixes: automatic separation of development and production databases so agents cannot touch production.
AI Engineer · Your AI Isn’t the Problem. Your Infrastructure Is. — Jiachen Jiang, Coder
Recommendation · MoneyPaden Gayle recommends finding the consequential action, naming its owner, and deciding what happens when the system is wrong.
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers
Recommendation · MoneyPaden Gayle notes that data owners ask who agreed to this use of documents, and warns that using client documents for AI processing without the data owner's agreement creates unauthorized data use.
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers
Recommendation · MoneyPaden Gayle recommends finding a person who can tell you which review applies to the intended use, and warns that designing a system without confirming which reviews apply creates deployment risk. Applicable reviews depend on the institution and use case, so confirm them with the people who own those decisions.
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers
Recommendation · MoneyPaden Gayle recommends confirming that existing controls really fit the intended use, and building the smallest useful version (MVP) with a credible path of approval; skipping the control check creates compliance gaps.
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers
Recommendation · MoneyPaden Gayle warns that a review button only helps if the person can actually check the work; building a system where the analyst cannot verify the output makes the review button useless. A reviewer should be able to inspect the supporting record showing what was used to produce a result.
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers
Recommendation · MoneyPaden Gayle, voicing the risk team's perspective, warns that if the model's output reaches the next system without a named reviewer, wrong exceptions flow downstream unreviewed.
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers
Recommendation · MoneyPaden Gayle recommends asking who checks the content when the system drafts a response a customer will see, and warns that deploying a system that drafts customer-visible responses without a content reviewer creates unreviewed customer communication.
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers
Recommendation · MoneyPaden Gayle recommends asking who owns the action, what happens if it sends something wrong, and how to stop and recover it when the system sends a response automatically; without these, uncontrolled operational risk results.
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers
Recommendation · MoneyPaden Gayle recommends drawing the actual dependency chain — including the model provider, host arrangements, and your role in the operating service — and warns that deploying AI without doing so creates unmanaged third-party risk.
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers
Recommendation · MoneyPaden Gayle recommends collecting evidence for the next authority decision by asking: are the reviews overriding the drafts, which failures keep recurring, and can people recover when something breaks?
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers
Recommendation · MoneyPaden Gayle recommends asking which input was used, which configuration produced the output, what the reviewer saw, and who approved the action; failing to capture these records from the beginning makes it impossible to reconstruct consequential actions later.
AI Engineer · Deploying AI Inside a Bank Is Not an Engineering Problem — Paden Gayle, Applied AI Engineers