Principle · MindHormozi argues that just because you know how to win doesn't mean you should win, and it doesn't mean the game is worth playing — there might be a different, parallel, or superior game that would result in what you actually want.
Alex Hormozi · a video to watch if you're ambitious and in your 20s or 30s
Principle · MoneySam argues that the model is the brain of an AI system, and when building something that makes decisions on your behalf, the brain matters more than anything else. Agents make decisions and handle complex scenarios and branching paths, so if the AI is a yes man that guesses and never asks clarifying questions, it builds agents that make bad decisions. The pushback, clarifying questions, and 'are you sure' before it acts are essential when building systems that think and act on their own.
Ahrefs · Why I Switched from ChatGPT to Claude
Creator perspective · MoneyAnish Acharya argues that humans are a critical ingredient and that most work in an organization cannot be done fully autonomously. Assuming it can leads to over-reliance on AI. He notes an AI-native company still needs humans for sales, support, strategy, and exceptions, and someone to say 'here's the thing I think we should make' and be right about it. He also warns that expecting an agent to generate a good business idea without setting it in the right direction leads to failure.
Lenny's Podcast · Why companies are becoming a series of loops | Anish Acharya (a16z)
Principle · MoneyWhen building agent products, make the right choices obvious to users because customers will blame the vendor even when the customer made the mistake — and the vendor should accept that responsibility. Build agents with guardrails so they make fewer mistakes than humans would in the same product.
The Official SaaStr Podcast: SaaS | Founders | Investors · SaaStr 876: Shipping Enterprise AI Agents with the CPOs of Rubrik, Glean, and Harvey
Principle · MoneyPrioritize building company-wide context — tacit knowledge, idiosyncrasies, and unstructured internal information — as the foundation for AI to perform work rather than just retrieve information. The better a company establishes that context, the more of the perform piece AI can do instead of the human.
The Official SaaStr Podcast: SaaS | Founders | Investors · SaaStr 876: Shipping Enterprise AI Agents with the CPOs of Rubrik, Glean, and Harvey
Principle · SocialFor common questions (work, where you live, what you do for fun), have a flavorful answer with a fun backstory instead of a straightforward, boring, logical reply; the goal is to display cool things about yourself while slightly dragging out the answer.
Coach Kyle · From Hi to Coffee Date (LIVE DEMO)
PrincipleGabriel Chua warns that failing to run periodic goal audits lets long-running agents silently deviate from original goals, and not checking in on blockers like missing API keys or authentication issues leaves the agent stalled without you knowing.
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
PrincipleCharlie Guo advises evolving your Codex workflow from asking in individual turns to building loops, thinking about what the loop needs to check at each turn; staying in individual-turn mode caps your leverage.
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
PrincipleCharlie Guo explains subagents: they get used out of the box by default, and the model is good at figuring out on its own when it should hand off into subagents, though you can also tell it to think about delegating. Subagents keep context separate, with models communicating with each other, which helps keep context windows efficient, and Gabriel Chua adds they are particularly helpful in long-running tasks because they keep context well separated and let agents focus. Use subagents when the work primarily needs to be visible to the model, not to the user — like delegating to a subcontractor whose conversations you don't care about, only the returned work. Use thread-to-thread handoff instead when you still want to be in the loop and see everything happening (released roughly two weeks
endorsed
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
Creator perspectiveCharlie Guo shares a series of escalating questions he repeatedly asks himself to get from an individual ask to something significantly bigger: 'Have I tried asking Codex to do it?'; as the agent progresses, 'What blocked Codex from getting to the answer?' — checking whether it needed context or permissions it didn't have; building needed context into repeatable tools like skills or plugins; scaling from one agent to many by prompting Codex to implicitly delegate structure or orchestrating across multiple threads; and 'Why does this process need a human at all?' — taking the human out of every step that doesn't need one (e.g., a plugin can fetch an API key and set it up locally), while keeping humans in the loop only where they need to be. The overall goal is to figure out how to build the
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
Principle · MoneyKent argues that product engineers should take ownership and accountability over what gets built rather than treating implementation as their only job. He frames this as the core of the workshop: technical expertise married to understanding of the user and their actual problems significantly shapes the product's direction. He also warns that engineers who only listen to someone tell them what to do and turn it into code are easily replaceable, especially as AI agents become competent.
AI Engineer · Build the Right Thing: Product Engineering (Part 1) — Kent C. Dodds, EpicProduct.engineer
Principle · SocialCoach Kyle frames early questions from a woman (like 'how old are you?' or 'do you do this a lot?') as tests to expect and handle, viewing them as signs of investment rather than attacks, and recommends responding with humor, playful stories, and displayed intent instead of defensiveness.
Coach Kyle · A Realistic Approach to a Single Woman Sitting Alone on a Bench (Infield)
Creator perspective · MoneyKent summarizes that getting down to the why-why-why and turning it into a job statement helps ensure you're building the right thing, and that understanding the job probably means you don't need the complexity of the originally requested solution (e.g., facial recognition).
AI Engineer · Build the Right Thing: Product Engineering (Part 2) — Kent C. Dodds, EpicProduct.engineer
Creator perspective · MoneyKent argues that a requested feature (like facial recognition) is not the job itself — the request and the job are two different things — and that repeatedly asking 'why' digs past the request down to the underlying job to be done.
AI Engineer · Build the Right Thing: Product Engineering (Part 2) — Kent C. Dodds, EpicProduct.engineer
Creator perspective · MoneyChanging a system prompt to fix one issue (e.g., tone) can cause unexpected problems elsewhere (e.g., hallucinating product features). Every prompt potentially affects every kind of input users send, and since the prompt is a huge block of text, you can't manually test every combination. Without evals you're playing whack-a-mole; with a faithfulness eval you'd catch a hallucination spike before shipping.
AI Engineer · From Vibes to Production: Evaluating and Shipping AI Agents That Work 101 — Laurie Voss, Arize AI
Creator perspective · MoneyBorrowing the Swiss cheese model from safety engineering, the speaker argued for stacking multiple layers of defense: code evals catch format issues but miss semantic problems; LLM judges catch reasoning gaps but miss subtle hallucinations; human review catches the subtle stuff but cannot scale. No single eval catches everything — the combination gives coverage.
AI Engineer · From Vibes to Production: Evaluating and Shipping AI Agents That Work 101 — Laurie Voss, Arize AI
Principle · MoneyLaurie Voss argues the real value lies in the eval-iterate cycle — run an experiment, change your prompt, run the experiment again, over and over — not in the score itself. The cycle: run the evals, look at the failures, read the explanations, identify a pattern, and adjust your prompt (or get Claude to adjust it for you). 'Did it get better?' is a question that can only be answered by evals, and evals let you move from 'I think it's working' to 'I can prove it's working.'
AI Engineer · From Vibes to Production: Evaluating and Shipping AI Agents That Work 101 — Laurie Voss, Arize AI
Creator perspective · MoneyWhen you cannot say what 'works' means, you cannot say the agent doesn't work; for a financial analyst agent, ask 'What does a good report look like?' to define success criteria.
AI Engineer · From Vibes to Production: Evaluating and Shipping AI Agents That Work 101 — Laurie Voss, Arize AI
Principle · MoneyWhen you change a prompt and rerun, you must check both whether the fix worked and whether it broke something that was previously working — changing a system prompt to fix one issue can cause hallucinations elsewhere in the application.
AI Engineer · From Vibes to Production: Evaluating and Shipping AI Agents That Work 101 — Laurie Voss, Arize AI
Principle · MoneyLaurie Voss lays out the full loop for building AI products: define what you want, build it, measure how well it works, ship it, monitor it in production, and iterate based on what you see. The condensed loop is instrument, trace, eval, and iterate — each step feeds the next. For AI products specifically, the measurement step is where most teams fall down, and evals are how you measure.
AI Engineer · From Vibes to Production: Evaluating and Shipping AI Agents That Work 101 — Laurie Voss, Arize AI