Pedro Lopez explains that CLIs invoked by agents cannot assume a human is present to answer interactive prompts; such CLIs get stuck. Inputs should be exposed via flags, and credentials via environment variables and config files so setup can happen out of band.
When starting with a customer, be transparent about three things: show what works (state the reliability level they can trust), tell them what you're doing to improve (acknowledge known gaps you're investing time to fix), and tell them what is out of scope — if something doesn't work, say so and don't let them try it.
Commercial context: The creator presents this as their own offering and directs viewers to get it.
Viren Baraiya walks through an SRE agent as a remediation loop: step one is a call to the LLM, whose output is the steps the agent should do; the harness then executes those steps as a deterministic workflow. The loop first understands the root cause of the problem, reacts to it, observes the output, and then runs another loop to plan the next set of steps — essentially a remediation loop that runs twice. The agent's job is to understand what's going on in the current system, plan what should happen next, and execute on those things.
Engineers should optimize for this new world by decomposing needs into their simplest chunks, which lends to understanding, simpler code surfaces, and control of code bases. Teams used to break a feature into small atomic pieces they could reason about — small enough to hold in your head.
Review service boundaries, data flows, state transitions, and failure modes as the compressed review surface. Leave the main process or workflow as the reviewable surface with implementation details pushed to the leaves. Gabriel Martinez also vouches for declarative code and architecture patterns that create layers humans can actually reason about.
The answer to AI slop is conventions, standards, documented flows, small reviewable surfaces, and clear ownership boundaries and definitions of done. The more obvious the path, the less room there is for slop to hide. With proper conventions, intent is more easily dropped into place.
Greg created a set of policies and a skill called 'Grumpy Engineer' (internally 'Garfield') to review agent-written code. It runs a sub-agent per policy; each sub-agent either gives feedback or stands down. The loop repeats until every sub-agent stands down and validates the code, and only then does Greg read the code himself.
Automattic runs two-week in-person enablement programs structured as 50% facilitated learning and 50% real project work. Internal workshop hosts run sessions, participants bring real work or tools/dashboards they want to build (including new skills or MCPs), peer workflow sharing is encouraged, and project demos happen at the end of each day.
Dru Knox recommends setting up a control plane with three components: an issue tracker that kicks off agent work, a review system, and a way to standardize and distribute workflows.
endorsed
Dru Knox recommends standardizing and distributing workflows via a skills registry or a shared GitHub repo where skills that improve agent quality are pushed.
endorsed
Dru Knox recommends moving all work into an issue tracker so every task starts as an issue that gets sent to a headless agent running in a sandbox.
endorsed
Dru Knox recommends setting up a control plane with three components: issue tracking (kick off agent work from tracked issues), review (GitHub PR review is probably the easiest), and workflow distribution (standardize and distribute workflows, playbooks, and skills via a skills registry or shared GitHub repo).
Anish Acharya suggests imagining your product costs $1,000 or $10,000 a month and asking what it would have to do to justify that price. He frames price as a measure of product-market fit and argues that expensive consumer software is a new and important opportunity, urging builders to think about extraordinarily expensive consumer products where every part of consumer discretionary spend is up for grabs.
Anish Acharya's core advice is to just make more things: come up with a project, ship something once a week, and use the project as a chassis to try all the new models, ship things, talk about them, and build your own intuition. He adds that it's better if the project isn't important with a capital I, and to keep investing in it with the model as a tool rather than a goal. He also pushes himself to ship something with every new model that comes out.
Anish Acharya observes that users can switch between similar AI coding products quickly because the underlying models are not that different — what matters is the harness and UX. He concludes there is major opportunity in user experience as a moat, or at least as a way to buy time to find something durable, and recommends focusing on craft and user experience.
Anish Acharya describes a bug fix loop: a bug report comes in, a repro gets generated, a bug fix gets created, the fix gets reviewed, and if it is high risk a human confirms it's okay to ship to prod, while if it is low risk it just gets shipped. Optionally, you email the customer to say 'hey, we fixed the bug you reported.'
Anish Acharya recommends thinking about every function as an agent loop that goes from input to impact. Your job is to figure out where it gets blocked or goes wrong and give it more context, insight, and direction. When an agent fails, identify whether it's a knowledge gap or a data gap, supply the missing context or data, and the next time it shouldn't have to call you.
Tim's answer to the benevolent-dictator mistake is to empower people early: write down your principles and guardrails, then have the courage to let people make decisions. Make people make decisions — the earlier you start, the smaller the decisions they can begin with. If you notice you are being a benevolent dictator, stop and empower people instead.
This is the speaker's personal recommendation from his own experience, not a validated method.
Kent recommends going out and watching your actual users use your software in their real environment — his shorthand is 'get on the truck,' from a story where a boss asked an engineer whether he had ever ridden along with truck drivers using their software. Seeing users in context is humbling and reveals dozens of concrete improvements (he mentions thinking of around 30) you would never identify from your desk.
Kent advises not turning feature requests directly into implementation — including not building an app that takes a user's request, sends it to an agent, and automatically implements it, which he says would produce a terrible product with no vision, taste, or judgment. Each feature request requires your product judgment, and requests shouldn't be nailed onto the product you already have.
Define a rubric for what a correct extraction looks like for your documents, then use an LLM as a judge against that rubric to evaluate extraction outputs.
Set up Sales Navigator reports to surface the people most likely to help you, then build a referral prospecting list from former colleagues, your boss and boss's boss, cross-functional leaders, veteran reps in your space, and your company's current customers, working with your CSM to get connected to those customers.
The creators behind most of what cleared in Money.
11494 cleared insights match
2032 cleared insights match
1148 cleared insights match
Choose sources → to get a library of your own and a daily brief.
