37,617 results · Most relevant
Pienaar 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.
To 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.
The 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.
The 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.
Jan Č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.
Using 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.
To 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).
Build '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
Require 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
In 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
Tara Seshan recommends identifying the eigenquestion — the specific most important thing to test. Hypothesis definition is the most important thing, and any grand strategy beyond the core hypothesis is not relevant. Be as pointed as possible about your core hypothesis.
Tara Seshan distinguishes two types of writing: 'writing as thinking' (outlining, writing prose, cutting, editing, iterating to get ideas in line) and 'writing as reporting' (status updates, summaries). She happily automates reporting with AI but never automates thinking. She starts and ends the writing process herself, using AI only in the middle for research, data, or idea pushback. She also advises writing the first draft yourself and not using AI to improve your writing.
Richard Socher emphasizes that when giving an AI a reward function, you must articulate exactly what you mean, as the AI will optimize the literal instruction, not your intent. He illustrates this with the example of an AI hacking a CSAT metric by creating bots if told to 'make this number go up' without specifying means.
Richard Socher emphasizes that reward engineering is one of the most crucial bits for auto-research, especially to avoid reward hacking. He advises starting by carefully defining the objective and notes that the longer the time horizon of the tasks, the harder and more clever you must be.
For a bootstrapper, a feedback loop longer than 12 months is dangerous because you risk wasting years of your life. The opportunity cost of spending 12-18 months on a long sales cycle is significant. If you have a long sales cycle, look for a vertical where something closes sooner to optimize learning speed. Evaluate whether you can learn faster than a long enterprise sales cycle by finding smaller customers or an MVP approach. If you pursue a long sales cycle, either raise funding, have personal runway, or do it nights and weekends. If you haven't closed a deal, it is very hard to raise funding unless you have a great network or a prior exit.
Push single leg squats heavy to transfer strength to speed. Use the Garage Strength single leg squat roller for heavy single leg squats. Use velocity-based training, pushing the weight as high as possible without going below 0.45 to 0.5 meters per second on average (not peak average). Athletes can push loads upwards of 400 pounds using this method.
Jeff Cavaliere recommends finding exercises that adduct the arm across the chest to train the chest to become more active. This includes floor flies with dumbbells (if no cable machine) and cable bench press (if available). He notes that floor flies avoid the shoulder vulnerability of unsupported bench flies.
The creator advises staying relaxed on a date and sitting at a close distance rather than across a far table with a formal vibe; sitting far and formal kills the relaxed close dynamic.
The creator discourages running very logical, formal conversation where you bombard her with questions, having zero laughter, and being afraid to play intent; his explanation is that she doesn't feel the spark because you don't create the spark.
The creator advises opening the date with a little bit of intent while not saying anything super flirty at the very start, because the date has literally just begun; with the right vibe, delivery, and positioning you can still create a powerful result early on.
Choose sources → to get a library of your own and a daily brief.