33,353 results · Most relevant
Huberman recommends a 13-minute daily meditation for 8 weeks, based on a Wendy Suzuki lab study, to significantly improve focus and concentration, mood, and stress — with additional reported improvements in sleep and memory. The protocol: set a timer for 13 minutes, sit or lie down, close your eyes, and focus on your breathing, ideally nasal breathing, bringing awareness to a point about an inch inside your forehead.
Hormozi offers a sequence of questions: am I the person who designed this game? If not, do I want the prize that comes with it? Am I willing to pay the price or sacrifice required to win, and is that globally worth it?
Hormozi advises that if you're playing a game right now and losing, ask yourself whether it's a game that, taken to its natural extreme, you actually want to win — and calculate both the price of winning and the benefit of winning.
Hormozi advises asking what game you are playing only because you're comfortable in it, understand its variables and players, and know how to win — and to identify the games you're playing consciously or unconsciously.
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.
The coach says most men play it too safe and try to only go for an IG or, even worse, a Snapchat when closing. He advises going for the phone number first, and then if you actually have a good Instagram, you can also do the Instagram. He describes the IG-only failure pattern: a friendly (not flirty) interaction, an IG exchange, DMs and story comments, then the woman stops responding when he goes for a date.
Don't stay on one conversation topic so long that the thread dies and the woman ejects out of the conversation. Take a proactive approach to carry the conversation in an engaging way and then switch topics. Anytime you notice something about her, point out that observation to switch onto a completely new topic — e.g., noticing her accent and asking where it's from, or even better, making a guess about where it's from. Small talk like the weather is okay briefly, but if an indirect topic lingers too long, the conversation dies and the woman is gone.
Get-to-know-you conversations follow predictable questions — where you're from, do you live here, what you do for work, what you do for fun, what you're into, your hobbies. The coach advises preparing flavorful, story-based answers in advance for these, since the way you answer matters more than the content of the job title itself. A flat, uncertain way of answering doesn't sound like a confident guy who will lead a woman, while cool answers create intrigue and attraction.
The coach advises injecting flirtatiousness — teasing or intent — within the first two to three minutes of an interaction rather than waiting until minute four. The student's interaction went three or four minutes with no additional teasing or intent beyond the initial open, which the coach diagnoses as lacking flirtatiousness. A flirty line like 'you could come visit me' hits harder if you've already dropped intent, push-pull, or teasing earlier in the conversation.
When approaching a woman on the street, open from a safe distance so she has time to look up, acknowledge you, see you smiling, slow down, and stop before walking past. Opening too close, too quietly, and without a smile causes women to blow past you and keep walking.
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.
A step-by-step method for converting a good daytime interaction into an instant date: check her availability, lead her to a nearby coffee spot, keep the ordering phase light, then move to seated conversation.
Gabriel Chua describes side threads: you can create one with the slash side command alongside the main thread to focus on a specific issue, and use it to give the agent targeted help (e.g., credentials for signing in) when you anticipate it needs assistance. Ask the agent in a side thread what it has done in the last hour, what it plans to do next, and whether anything can unblock it; the side thread can update the main thread with resolved information. Side threads are ephemeral and get stale, so communicate any context you want to keep back to the main thread. He also suggests asking Codex to send Slack messages — via the Slack plugin, reply to a thread with a summary of what's done, what's not, and any blockers — since blockers like authentication issues or API keys are common, and he'd
endorsed
Charlie Guo recommends embedding Codex into your product using the AppServer, letting users power the product with their ChatGPT subscription and token budget.
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.
A closing sequence where the speaker first asks what she's up to right now, then states what he was considering doing (e.g., getting coffee or tea) without asking her thoughts, creating an implicit invitation that lets her reveal availability without a direct ask.
Choose sources → to get a library of your own and a daily brief.