Recommendation · MoneyThe first takeaway from the case study is to prioritize user experience. Jake tanked while focusing on technical SEO basics, then switched to user experience and giving people what they want — which produced massive growth. He also turned down ads significantly because he believes they deliver a bad user experience, accepting a direct revenue hit, and says delivering high quality and getting information to users quickly makes people remember you.
The revenue-hit-was-a-blessing framing is Jake's personal belief ('I feel like that hit was probably the best thing that could have happened to my business').
Ahrefs · The Greatest Google SEO Recovery of All Time?
Recommendation · MoneyThe host repeatedly recommends automating tax collection because nobody wants to get in trouble for not knowing the tax rules. In the EU specifically, digital subscriptions are subject to VAT, so she recommends using Stripe Tax when selling digital subscriptions there.
AI Engineer · https://www.youtube.com/watch?v=T3wRyXg_yVg
Recommendation · MoneyKim Maida recommends using a security token service to manage agent access control with delegated, task-based policy governance, and routing every agent request through the STS and policy evaluation before a token is granted and the agent is authorized to act.
AI Engineer · Your Agent Is a Lethal Trifecta (And What to Do About It) — Kim Maida, Keycard
Method · MoneyStep one: create an environment via the Environments API (V1 environments) to define the sandbox template, including networking (unrestricted or restricted to specific domains/MCPs) and packages installed on the container. Step two: create the agent, giving it a name (e.g., 'joke teller'), choosing a model (Opus 4A, Haiku, or Sonnet), providing a system prompt (e.g., 'You're a comedian. Find a fresh joke on the topic. Deliver it well.'), and providing tools (e.g., the agent tool set: bash, read, write, grep, etc.). Step three: create the session, which takes an agent ID and an environment ID.
Method, not a verified protocol.
AI Engineer · https://www.youtube.com/watch?v=Uv0nAf_7tyU
Recommendation · MoneyNnenna Ndukwe recommends starting a quality-driven agentic engineering process by defining what code quality means to you and your team. The standards then need to be codified somewhere your AI can extract them so it can adhere to your code standards regardless of interface, and made distributable across all interfaces: CLI, IDE, and CI workflows.
AI Engineer · How to Build Quality Gates into Agentic Coding Workflows — Nnenna Ndukwe, Qodo AI
Recommendation · MoneyInstead of vague prompts like 'create a user login screen in Python', specify all security requirements the agent should implement, such as a login function taking email and password, rate limiting, and parameterized queries.
AI Engineer · AI Security Engineer Foundations + Certificate — Javier Garza, Snyk
Recommendation · MoneyThe creator recommends building for agents as well as people if you want to win in the next era of consumers, arguing it might today be more important to build for agents than for people. Going forward, 'make something people want' (from Y Combinator, the startup factory from Paul Graham) should also mean making something that agents want. If you don't build for the agent economy, your product might not win or be successful.
AI Engineer · https://www.youtube.com/watch?v=nSkmXakJ6eo
Recommendation · MoneyThe evaluation is probably the most crucial part of an AutoResearch system: you want a very simple way of allowing the system to evaluate every solution it generates, and you want it to output a single scalar metric. Ask yourself two questions for the metric and goal: what do I want to improve, and is higher or lower better? Make your eval fast, cheap, and low-noise, because this leads to your ability to run more steps under a fixed budget or time constraint, and low noise makes both you and the agent more confident while hill climbing.
AI Engineer · Parameter Golf with AutoResearch — Vayum Arora, Zhengyao Jiang, Dixing Xu & Dhruv Srikanth, Weco AI
Recommendation · MoneyThor Schaeff recommends using a native audio model like Gemini Live instead of a cascading voice agent pipeline when fluid multilingual switching is needed, because the native model can switch very fluidly between different languages.
AI Engineer · Can Your Agent Hear You Now? Building Live Voice Agents with Gemini — Thor Schaeff
Recommendation · MoneyThor Schaeff recommends sending real-time text, audio, and video frames to the Gemini Live model over a WebSocket connection, and streaming the audio chunks returned by the Gemini Live API into the application.
AI Engineer · Can Your Agent Hear You Now? Building Live Voice Agents with Gemini — Thor Schaeff
RecommendationAll the agent's loop information should be available in the PR itself so a human can read it, validate the code, do code review, and ship. Keep a human in the loop for code review on agent-proposed fixes — the speaker recommends this as a limit on how far to take self-healing software.
endorsed
AI Engineer · Building Self-Learning Loops for Your Agent — Fuad Ali, Arize AI
RecommendationGet tracing started first: if you're not collecting tracing, nothing else works. It takes sub-ten minutes on your own agent.
endorsed
AI Engineer · Building Self-Learning Loops for Your Agent — Fuad Ali, Arize AI
Recommendation · MoneyEvaluation is multifaceted, so you can't just use LLM-as-a-judge alone and expect it to give you everything — checking a dataset for a hundred problems only tells you those hundred issues don't exist; there could be a thousand other issues. Use LLM-as-a-judge as one generic layer, send judge outputs to human reviewers who cross-check the judgments, and for search data evaluate against real-time information as an additional layer. Find a union of all the different layers of evaluation to gain enough confidence in your dataset.
AI Engineer · Teaching Agents to Search with NVIDIA Data Designer — Dhruv Nathawani, NVIDIA
Recommendation · MoneyYoni Michael recommends designing eval questions whose answers can be deterministically scored, arguing LLM-as-judge is overused when deterministic scoring is possible. Deterministic scoring reduces variance and cost across runs and makes you happier long term. He also recommends creating questions where you can structure a gold answer and check the agent's answer against it, and building a deterministic check that verifies the agent cites all expected evidence.
AI Engineer · The Data Context Layer for Agents — Yoni Michael & Brandon Callender, Typedef
Method · MoneyBrandon Callender describes building the context graph for data: ingest the dbt project, pull in all the SQL, parse it, and link everything together; query the data catalog to get information about the physical table corresponding to a dbt model and pull it into the graph as well. He emphasizes that they read information from the catalog to form the context graph — the catalog and context graph coexist rather than being redundant.
Method, not a verified protocol.
AI Engineer · The Data Context Layer for Agents — Yoni Michael & Brandon Callender, Typedef
Method · MoneyYoni Michael lays out a method for measuring tool adoption: use two different prompts trying to answer the same question with the same tool set, write an eval that examines all tools in the trace to get adoption numbers, then change the prompt to increase the tool usage percentage (he reports going to 72% tool usage after changing his prompt).
Method, not a verified protocol.
AI Engineer · The Data Context Layer for Agents — Yoni Michael & Brandon Callender, Typedef
Recommendation · MoneyAlways be as deterministic as possible first, and only use LLMs when resolving ambiguity or doing things models are actually really good at; use the LLM only for the human-readable parts — understanding business names, summarizing model utility, or resolving ambiguity from the deterministic layers.
AI Engineer · The Data Context Layer for Agents — Yoni Michael & Brandon Callender, Typedef
Recommendation · MoneyMake business definitions first-class constraints for the agent — not just a comment in some YAML file — so the context layer catches definition changes before implementation; that is the line between a syntactic refactor and a change a human can actually trust.
AI Engineer · The Data Context Layer for Agents — Yoni Michael & Brandon Callender, Typedef
Method · MoneyBrandon Callender describes an eval scenario: inject a diff into the code base that introduces a bug, then ask the agent to fix it, and test that the agent looked at the right places, checked the right things, and didn't fix the bug upstream or downstream with a band-aid. He also describes forcing the agent to work backward from a dashboard symptom upward through the dependency tree to find the root cause, then asserting it fixes that problem, and notes you can make eval tests easier or harder by changing the prompt language — e.g., 'I think there's a problem with model XYZ' versus 'my dashboard Y is having this issue where this number is doubled. I don't know why'.
Method, not a verified protocol.
AI Engineer · The Data Context Layer for Agents — Yoni Michael & Brandon Callender, Typedef
Recommendation · MoneyYoni Michael recommends a recipe for building really solid, honest evals: mine real task candidates out of your corpus as the first step, build a deterministic, anchored score for your evals as much as you can, run your evals many times over rather than once, and put in examples of things your agent may not necessarily be good at. He adds that giving your agent very easy and simple evals does no one any service.
AI Engineer · The Data Context Layer for Agents — Yoni Michael & Brandon Callender, Typedef