Report · MoneyTejas gives the two reasons for evals: (1) ahead-of-time reliability in contrast and complement to just-in-time reliability from harnesses, and (2) making sure people can't do dangerous things. A solid set of evals helps you quickly find what your agent is not doing properly, mitigating against exploits on a security level. Any time you have non-deterministic data — inputs, outputs, or both — you need some type of evals.
AI Engineer · Evals in AI: A Deep Dive — Tejas Kumar, IBM
Principle · MoneyIf an account manager has not delivered value on an account through the CSM and the existing customer relationship, there is no pipeline — the AM should focus on helping the team deliver more value rather than hunting new accounts, unlike an AE who can simply move on.
30 Minutes to President's Club | No-Nonsense Sales · #604 - Upsell & Expansion Masterclass: 7 Lever to Grow Any Account
Principle · MoneyIf you provide value for a customer but they don't acknowledge it, you didn't really create the value — you must communicate it back and get them to acknowledge it. Value is what gets the customer to ask for more projects, and more value is how AMs create commercial gain inside the account.
30 Minutes to President's Club | No-Nonsense Sales · #604 - Upsell & Expansion Masterclass: 7 Lever to Grow Any Account
Principle · MoneyWarrick's argument for why Temporal: when you need durability in an agent system, Temporal standardizes failure handling and state management with out-of-the-box primitives applied to your codebase. Durability means the system can come down, recover, and manage complex state in distributed systems; if anything falls over, the durability layer lets it resume where it left off. She advises building durability into the harness picture when you want agents to survive production, and giving agents structure so they work reasonably well in production.
AI Engineer · The Human Is an Async API — Melanie Warrick, Temporal
Principle · MoneyWarrick's key design principle: when a human submits a change or needs to approve something, only the affected event/workflow pauses while other agents, orders, and workflows continue processing. This is why the system can wait for a human response for minutes, days, or weeks — pausing affects only that one specific event.
AI Engineer · The Human Is an Async API — Melanie Warrick, Temporal
Principle · MoneyWarrick's guidance on when to insert a human: it is a case-by-case evaluation for the problems you're solving, with the big consideration being that the cost of being wrong is high (especially from a security standpoint). She warns that alert fatigue is real — people start saying yes to every question — so you must balance the cost of being wrong against alert fatigue. She notes models are probabilistic and hard to make reliable, and that efforts to improve them continue but they remain probabilistic.
AI Engineer · The Human Is an Async API — Melanie Warrick, Temporal
Creator perspective · MoneyHarald Kirschner argues it's not about using more AI day to day (token maxing), it's about evolving the whole system of shipping software to make better use of AI along the whole process. That system evolution is what makes velocity actually work and doesn't just generate more code. As you use agents and more AI, things break and you have to rethink how you work.
AI Engineer · How VS Code Went from Monthly to Weekly Releases with AI — Harald Kirschner
Creator perspective · MoneyHarald Kirschner lays out the problem ladder: shipping code faster is the easy part — a 100x engineer builds a skill/MCP plugin system and slowly more people adopt the same patterns. Once you ship faster, you get into code review and how to ship high-quality code that doesn't constantly break. Shipping binaries to user machines means if something breaks, recovery is even more costly. Once you hit velocity with shipping high-quality code faster with confidence, the next question is how do you know you're shipping the right thing or if you should ship this thing. AI kicks in to actually learn faster in the end and ship better products — applying product taste and applying that learning — which a lot of people miss out on as they write more code.
AI Engineer · How VS Code Went from Monthly to Weekly Releases with AI — Harald Kirschner
Principle · MoneyMeegan proposes applying the equation profit equals revenue minus cost: the agent is just another line item and should give you more than it takes. A browser agent gives you a task completed for your customer, repeatedly — ideally. The goal is a dynamic system that wades through ambiguous problems while completing tasks repeatedly when the environment stays the same.
: none
AI Engineer · Why 99% Accurate Browser Agents Still Fail — Derek Meegan, Browserbase
Principle · MoneyMeegan's principle: take steps out of the model's responsibility that do not need to be there, containing the agent to only the area of ambiguity necessary. Reducing the agent's steps leads to lower unit costs, higher performance, and easier maintainability, and increases the probability of achieving the desired outcome.
: none
AI Engineer · Why 99% Accurate Browser Agents Still Fail — Derek Meegan, Browserbase
Creator perspective · MoneyCode generation is only 14-16% of the value stream. Time savings from AI are often outweighed by non-AI factors like meetings, context switching, and dev environment friction. Identify and fix the true bottleneck.
AI Engineer · The State of AI in Software Development: Data from 400+ Orgs — Justin Reock, DX
Principle · MoneyGrant employees high agency and autonomy to execute without excessive policing or fear-based friction. This trust enables speed and allows employees to move quickly, make mistakes, and learn.
high
The a16z Show · Building a Team at AI Speed | Harvey’s Maggie Landers
Principle · MoneyTrust is the foundational value that enables high agency, rapid experimentation, and hiring quality. Leaders prioritize holding onto trust as the company grows to maintain speed and avoid bureaucratic bottlenecks.
high
The a16z Show · Building a Team at AI Speed | Harvey’s Maggie Landers
PrincipleTreat AI agents as untrusted entities with oracle-like capabilities when designing threat models. The untrusted side in a threat model is assumed to be an oracle. The question is whether information can be extracted from the trusted side.
The a16z Show · Aaron Levie, Steven Sinofsky & Martin Casado: How Do You Secure a World of AI Agents?
PrincipleThe early internet was plagued by viruses and security failures, but society continued building it and learned to make it safer. This historical precedent suggests AI should follow a similar path of iterative security improvement rather than halting development.
The a16z Show · Aaron Levie, Steven Sinofsky & Martin Casado: How Do You Secure a World of AI Agents?
PrinciplePacing AI development is logically impossible without a published schedule or known baseline rate of development. Claiming to be 'pacing' without a baseline is disingenuous. If researchers genuinely believe in existential risk, they should nationalize the technology; if not, it is an HR/retention issue.
The a16z Show · Aaron Levie, Steven Sinofsky & Martin Casado: How Do You Secure a World of AI Agents?
PrincipleCurrent access and security models are not granular or performant enough to handle AI agent swarms. A different access and security model is needed going forward, leveraging AI to handle the usability complexity of multi-layer security.
The a16z Show · Aaron Levie, Steven Sinofsky & Martin Casado: How Do You Secure a World of AI Agents?
Creator perspectiveZach Lieberman states that he has a group of graduate students thinking about future tools for artists and designers. He teaches them about art and wants them to engage with history. He advises students to be like a sailor, using the wind of hype to go in their own direction, and to engage with the tools and voice of today.
Figma · 13 Designs that Inspired MIT Professor Zach Lieberman I Source Material
Creator perspectiveOfir Ehrlich and Gonen Stein argue that a company's proprietary data is its primary competitive advantage, more valuable than models or compute, which have near-zero switching costs. This data, often locked away, has become a strategic moat.
No Priors: Artificial Intelligence | Technology | Startups · Rethinking Legacy Data Infrastructure with Eon Co-Founders Ofir Ehrlich and Gonen Stein
Creator perspectiveGonen Stein and Ofir Ehrlich state that high-quality, non-synthetic data reflecting real-world complexity is scarce. To build significant AI applications, one must interact with real-world companies and their data, as synthetic data often fails to represent real-world complexity.
No Priors: Artificial Intelligence | Technology | Startups · Rethinking Legacy Data Infrastructure with Eon Co-Founders Ofir Ehrlich and Gonen Stein