MethodDr Ghayas Issa describes the workup for suspected differentiation syndrome: check blood counts for an increase in white count (sometimes associated with differentiation) and look for leukemia cells turning into normal cells; obtain a chest x-ray because pleural or pericardial effusions can occur; perform an echocardiogram if there is a pericardial effusion; and check kidney function.
Consequential creator advice requires independent verification before Today can promote it.
Method, not a verified protocol.
Research To Practice · Acute Myeloid Leukemia — An Interview with Dr Ghayas Issa on the Role of Menin Inhibitors
Method · MoneyArmand describes the call structure he taught SDRs: an opener, then when the prospect says no, leading into a 'problem proposition' that leads with the problem before the solution (illustrated by his Carta example about CFOs finding it ridiculous to pay lawyers to issue stock options). For the spreadsheet objection, he used the 'Mr. Miyagi method' of agreeing with the prospect and selling a test drive. He reports that these three things got SDRs good on the phones, moving cost per appointment from $50 to $200 and meetings per SDR from four to eight.
Method, not a verified protocol.
30 Minutes to President's Club | No-Nonsense Sales · #606 - How To Build An Elite Outbound Sales Team (Get Reps Dialing Fast)
Method · MoneyArmand describes five meetings that can run 90% of SDR teams: a Monday morning meeting (MMM) that injects energy and focuses on activity, Teardown Tuesdays and Thursdays (30-minute sessions reviewing three cold calls, two cold emails, or two to three accounts, giving coaching without adding much calendar time), Wednesday one-on-ones for individual coaching, metrics review, and role play, and Friday team dials that end the week with energy and focus on activity plus culture. The week is bookended by energy-focused meetings on Mondays and Fridays with skill-focused sessions on Tuesdays and Thursdays.
Method, not a verified protocol.
30 Minutes to President's Club | No-Nonsense Sales · #606 - How To Build An Elite Outbound Sales Team (Get Reps Dialing Fast)
Recommendation · MoneyBefore addressing the team publicly, conduct 16 hours of back-to-back one-on-ones with every team member, using a 'between you, me, and the wall' conversation to privately share the turnaround plan. Winning over individuals first means peer pressure helps win over the rest of the group.
anecdotal
30 Minutes to President's Club | No-Nonsense Sales · #606 - How To Build An Elite Outbound Sales Team (Get Reps Dialing Fast)
Method · MoneyArmand describes a revamped SDR interview process. A recruiter screen cuts about 50% of the applicant pool. The second step is a mock cold call, where the first call is expected to be bad; the interviewer looks for whether the candidate's gears are turning and how much they researched, gives no more than two points of specific feedback (e.g., leading with a problem proposition instead of a pitch), and treats no change on the second call as a massive red flag. After the mock cold call the interviewer should know if they have a 'triple A' hire. The final stage is a triple onsite of three back-to-back interviews: a mock cold email (written live or drafted beforehand, testing whether the candidate applied prep and used their brain), a rep filtering test (narrowing 40,000 companies to 25, with
Method, not a verified protocol.
30 Minutes to President's Club | No-Nonsense Sales · #606 - How To Build An Elite Outbound Sales Team (Get Reps Dialing Fast)
Recommendation · MoneyA prospecting turnaround can often be achieved not by increasing activity or improving phone skills, but by removing waste in the prospect list. Categorize personas into A/B/C tiers and replace all C-tier prospects with more A-tier prospects without increasing overall activity. Don't reach out to personas that are a poor fit for your product (e.g., selling stock option management software to a Chief HR Officer).
endorsed
30 Minutes to President's Club | No-Nonsense Sales · #606 - How To Build An Elite Outbound Sales Team (Get Reps Dialing Fast)
Recommendation · MoneyPienaar recommends generating many different theories simultaneously to give the agent breadth and diversity of ideas, calling this Cleric's primary technique. The rationale: agents are excellent at relative ranking but terrible at absolute scoring of their own theories, so multiple candidate ideas beat asking for one scored answer.
AI Engineer · Your AI Agent Is Confidently Wrong About Production — Willem Pienaar, Cleric
Recommendation · MoneyPienaar recommends computing a baseline for production — extremely important in large environments — because most prod environments are in permanent disarray and chaos: engineers know which error logs to ignore and which metrics are unused, but an agent doesn't. Concretely, cluster logs and give the agent statistics on which logs recur daily and are common, not just raw logs; the same approach applies to metrics, object state, and many other things.
AI Engineer · Your AI Agent Is Confidently Wrong About Production — Willem Pienaar, Cleric
Recommendation · MoneyPienaar recommends using a topology or build dependency graph of the production environment. When the agent claims a causal connection between services, output all connections that actually exist and have another agent critique the claim — an effective way to introduce doubt and push the agent to go further if the claim doesn't map to a real connection.
AI Engineer · Your AI Agent Is Confidently Wrong About Production — Willem Pienaar, Cleric
Recommendation · MoneyPienaar recommends that when sub-agents hand context to each other, they build a case with evidence rather than just giving the answer. This mirrors what SREs do — 'I looked at this metric, and it was at this point in time' — hard evidence rather than 'prod is up.' If evidence isn't propagated, it loses fidelity and causes hallucination and overconfidence.
AI Engineer · Your AI Agent Is Confidently Wrong About Production — Willem Pienaar, Cleric
Recommendation · MoneyTo know whether techniques actually work beyond vibes, Pienaar recommends looking at verification and outcome in addition to diagnosis. The production incident response flow with agents is detection, diagnosis, and fix, and most folks only use agents for diagnosis. Cleric triangulates across many different signals what happened when a fix is applied — monitoring whether the engineer actually merges code that maps to the diagnosis — and checks for a return to normal in service metrics, logs, and baseline state. Muting an alert also shows a return to normal, which is why multiple signals must be checked. This outcome machinery exists to calibrate evaluation.
AI Engineer · Your AI Agent Is Confidently Wrong About Production — Willem Pienaar, Cleric
Recommendation · MindThe narrator recommends: identify one insecurity you have been quietly managing — you know it's that one because you spend a lot of time trying to hide it from other people. Instead of managing the insecurity right now, just say it out loud. If you feel comfortable, share the insecurity with one person you're close to. You'll probably find that the same feeling is true for whatever you've been quietly hiding, and by sharing your authentic self you'll stop spending so much time judging yourself.
Charisma on Command · This Is Not Confidence
Recommendation · MindThe narrator recommends that you can afford to be honest and name the vulnerable thing first before anyone else can use it to insult you. On a first date, instead of performing all dinner, you could start by saying 'I'll be honest, I always find the first few minutes of these incredibly awkward' — the other person will probably laugh because she was feeling the same thing, and the whole dinner can change from that point onward. In a meeting when asked about something you're not sure about, instead of bluffing, you could say 'I actually haven't done this before. Could somebody walk me through?' — and if you admit it, learn how to do it properly and do it well, six months later you'll be the one being asked to help others.
Charisma on Command · This Is Not Confidence
RecommendationJan Čurn recommends using MCP for standard remote access and CLI for local agent access/interface. This lets you provide all MCP protocol features through a single tool call all agents already know — Bash — hiding the full complexity of MCP (sessions, authorization, OAuth) behind it.
Endorsed with high confidence.
AI Engineer · MCP Doesn't Suck. Your Agent Does. — Jan Čurn, Apify
Recommendation · MoneyUsing web search, an agent can look at the repository itself, find breaking changes from the repo's changelog, and explain the migration in depth. For a code review agent, a rule might be: when the diff bumps a dependency or version, look at the upstream source to verify it is actually true, and then ground the review in what you find.
Stated as a suggested rule ('might look like'), not a mandate.
AI Engineer · Your Coding Agent Is 6 Months Out of Date — Jakub Hojsan, Exa
Recommendation · MoneyTo enable easy multi-agent systems, developers must solve four key layers: Transport (ordered/real-time delivery, retrying), Continuity (persistency, hydration, runtime binding), Conversation Abstraction (rooms, channels, participants), and Governance (identity, audit).
AI Engineer · Your Agents Are in Solitary Confinement: Why MCP & A2A Aren't Enough — Vlad Luzin, Band
Recommendation · MoneyBuild 'narrow startups' targeting very small user bases with high willingness to pay ($200-$300/month) to achieve high run rates without mass market scale.
high
The a16z Show · The Personal Agent Race Is Here | Anish Acharya & David Pawlan
Recommendation · MoneyRequire explicit user permission before an agent takes direct actions that impact the user (e.g., switching insurance), but allow proactive action for tasks requiring no user-side action (e.g., drafting emails, getting credits).
high
Contested by Jed (Harrison Stall) on AI Engineer
The a16z Show · The Personal Agent Race Is Here | Anish Acharya & David Pawlan
Recommendation · MoneyIn high-autonomy environments, employees must develop strong judgment ('spidey sense') to determine when to pause, seek feedback, or perform spot checks before pushing work live, balancing speed with quality.
high
The a16z Show · Building a Team at AI Speed | Harvey’s Maggie Landers
Recommendation · MoneyMost B2B demos should follow a specific cadence: Intro (with discovery), Agenda (setting expectations and the ask), Discover (problem story), Define the Problem (with prospect validation), Benefits for Decision Maker, Benefits for Influencer, and a Close.
MicroConf · SaaS Sales Demos: Why Getting a No Is Better Than a Yes