33,339 results · Most relevant
A complete myo-rep protocol: select an 8-15 rep max load (up to 20-25 RM if tolerated), do an activation set of traditional reps until rep speed slows noticeably, rest with 3-5 deep breaths while setting the weight down completely, then perform 3-5 rep mini sets matching the first mini set's rep count, capped at five mini sets.
A step-by-step teaching progression: set up with a clean grip and feet about a foot width apart, roll elbows high and rotate to rack position, do elbow roll drills to feel the upper back, use small elbow rolls to loosen wrists if hard, front squat with a slightly wider stance, muscle clean from the thigh without dropping under, then power clean from the thigh with explosive direction change. The full progression takes four to five minutes and is done daily as a warm-up.
A coherent multi-step sales approach: stay out of the price-matching game and play the value-surpassing game; itemize all elements of the service; use a price-match challenge script; frame the competitor's lower price as fair because they don't do the value-added things; use a conditional walk-away script citing what cheaper movers don't do; cite the 25% breakage statistic and frame the odds; anchor the premium with a worth-it question; and close with 'this is what it sounds like you really want, and that's what I can deliver.'
Coach Kyle lays out five checkboxes for going from a friendly, indirect conversation to landing a date in one interaction: (1) open with an observation or question, (2) transition the conversation to being about her, (3) introduce names around the 2.5-minute mark, (4) display intent after rapport is built, and (5) run a closing sequence to get her number and set up a date. He notes most men only do step one and never complete the rest.
Coach Kyle presents a five-level progression for approaching women: level one is greetings and compliments in passing, level two is briefly stopping anyone for a 5-15 second conversation, level three is making it flirty, level four is longer conversations, and level five is a full man-to-woman interaction where you get phone numbers and set up dates. He advises doing the rep of your current level enough times until your mindset shifts before moving to the next level, and notes each level includes a gradual mindset shift rather than a zero-to-100 jump.
A progressive sequence of plyometric exercises for people over 40, starting with a warm-up (PVC pipe walk, ISO hold, big toe work) and building through low box jumps, two-to-one box jumps, jump rope, single leg pogo hops, and lateral hurdle hops to build explosiveness, elasticity, and coordination.
The host walks through building a dynamic pricing sheet (coded with AI or an if-then Excel sheet) that calculates price automatically during a customer conversation: separate variable costs that scale with headcount from fixed costs like payroll, allocate fixed payroll per event based on capacity, and never show the internal cost number to the customer. He notes such a module can be built in a couple of hours.
Anthropic recommended storing long-term agent resources as YAML files in your codebase and building CI/CD pipelines that run Ant CLI with the checked-in YAMLs every time a resource changes, in a Terraform-like workflow. They noted Anthropic internally uses this same approach for durable long-term resources.
Define a main coordinator agent that can talk to agent B and C; agent B is the one processing custom tools, with the custom tool defined in agent B's definition; listen to that session thread to get the tool result back. Sub-agent threads are part of the same core session — you only interact with the main thread and the system delegates based on IDs.
Kevin's team built an MCP server in a day or two to expose access to their cloud environment and platform so coding agents could interact natively, because frontier models know the MCP protocol well. They refined the exposed tools and smoke tested runs before scaling up.
Put monitoring and auditing on agents — most people don't do this. Configure agentic tools to pull all agent activity into a log file with verbose logging (tools do a lot in the background that doesn't show in the UI), then run a background tool that greps the log and flags malicious behavior you may miss in the interface, such as checking secret storage. Background agent tasks are especially prone to unreviewed malicious behavior because the user isn't watching.
A practical method for AI threat modeling: use an existing framework (STRIDE, Maestro, Attack Trees, DREAD), cover each STRIDE category when designing, produce deliverables (architecture and data flow diagrams, threat catalogs, mitigation plans, security requirements), and redefine scope for AI to include LLM models, prompt templates and system prompts, context windows, memory stores, and accessible endpoints/APIs.
Put monitoring and audit on AI agents, because agents left unmonitored may do things you don't want. Configure agentic tool settings to pull all agent activity into a log file (verbose logging for every agentic tool you use), then run a background tool that scans the log file and monitors for unwanted behavior like checking secret storage.
Integrate AI threat modeling with whatever DevSecOps program your company has. Threat models need to evolve alongside application deployments: for every change pushed (pull requests, code changes, AI application changes), run scans and threat-modeling checks. Set up triggers such as webhooks so changes automatically trigger a scan; scan when infrastructure-as-code changes (e.g., monitor a Terraform file an agent creates so a scan runs the moment it changes); data pipeline updates and AI model deployments should also trigger scans.
A doer agent and a teacher agent iterate together on a browser task: the doer attempts the task, the teacher reviews screenshots and logs and writes corrections into strategy.md, which carries over to the next iteration. The loop runs until it converges, without prescribed iteration counts, success-rate targets, or token/time limits ('embrace the bitter lesson'). The converged output is a skill.md file for future agents.
A coherent train-to-deploy workflow on Fireworks AI: prepare separate train and eval datasets, launch training via the training agent or managed training (API/UI), monitor progress through the UI dashboard, and swap new checkpoint weights into the existing endpoint when ready.
In the intro notebook: set up the environment, import prompts and Data Designer, use a CSV of Wikipedia topics as the seed dataset, call the config builder with the seed dataset, add question difficulty (easy/medium/hard) with weights, add sub-sampler question types (easy = direct lookup or simple fact/definition; difficult = more detailed or obscure), add LLM-generated columns via addColumn with a prompt like 'You are an expert trivia question writer... topic, difficulty, question type', use Jinja templating so every prompt is unique and diverse, drop records that don't match the structured format, preview three records, then generate.
NVIDIA's pipeline for creating search training data: use Wikidata (a graph of Wikipedia topics) as the seed dataset; randomly sample an entity and do 5–8 hops along the graph (stay between 4 and 8 hops as a heuristic, since hops can go off-topic, e.g., a person's name leading to 'human being'); transform the seed entities into search riddles — simple, riddle-like questions the model cannot readily find on the internet; execute the search via the search tool (Tavily) to create a dataset with a search prompt and a search response; evaluate the data, train the model with it, and measure performance on a standardized benchmark. The seed collection algorithm can be run a million times to produce a million different hops.
Instead of asking the model ten things about a chunk of code at once, ask ten different questions about ten different smaller chunks of code that answer specific questions. For SQL: instead of asking the model to look at an entire block of SQL and tell you what all the columns mean, parse the SQL and ask about one column — here's the type, here's the comments — is this a measure? Is this a dimension? At that point, you can ask the agent to do classification and summarization, which are the things it's good at. If you want to weigh the answer more, give the model more prompt input to that single focus question — don't cram more questions in; give it more context to answer that single question with.
endorsed
The overall process of constructing knowledge graphs from unstructured text using an LLM is: gather data sources, chunk the data, vectorize it, extract nodes and relationships, then generate the graph. To build a knowledge graph from a source like the Neo4j Wikipedia page, gather all the text from the page and split it into chunks. Generate embeddings and vectors from each chunk of text. Extract entities and relationships from text chunks using an LLM. Manual entity/relationship extraction is possible, but using an LLM cuts down the amount of time extraction takes. Send the LLM a prompt instructing it to identify the entities and relationships requested from a given text and generate output in JSON format containing a list of JSON objects. Parse the LLM's entities-and-relationships output
Choose sources → to get a library of your own and a daily brief.