Recommendation · SocialThe coach criticizes the client's answer 'I'm wandering around the city center, just kind of checking out the city. I don't know' as stale, boring, flat, and lacking substance — it sounds like you have nothing fun going on in your life. He models a better answer: 'Well, honestly, I have the luxury of taking Fridays off from work. So it was just such a beautiful day out. And I just got to Miami literally a couple of days ago. So my first thought was, let's go check out the city center,' plus adding that friends recommended checking out downtown Brickle. A flavorful answer communicates excitement and that you have something cool going on.
Coach Kyle · How to Talk to Women in Public: Real Infield Breakdown
Recommendation · SocialFrame even mundane activities like walking around the city as deliberate, enjoyable choices with context — friends' recommendations, a beautiful day, the luxury of time off. A good answer about what you're up to includes having the luxury of taking Fridays off, it being a beautiful day, just having arrived in Miami a couple days ago, and wanting to check out the city center. Frame your job answer around the story of how you got into it and the parts of the job that are high-status benefits in your life.
Coach Kyle · How to Talk to Women in Public: Real Infield Breakdown
Recommendation · SocialInject intent, push-pull, or teasing early in the interaction (around minute 2-3) rather than waiting until minute 4. Use push-pull and teasing early to build flirtatiousness before making bigger flirty moves. A flirty invitation lands better when preceded by prior teasing and intent rather than delivered as a standalone injection minutes into a mostly neutral conversation.
Coach Kyle · How to Talk to Women in Public: Real Infield Breakdown
Recommendation · SocialOpen the woman from a safe distance and give her enough time to look up, acknowledge you, see you smiling, slow down, and come to a stop before going past you — the coach liked the distance and the way the student got her to stop. He also advised slowing down the delivery of the opener and adding more pauses, since there weren't enough pauses in the delivery.
Coach Kyle · How to Talk to Women in Public: Real Infield Breakdown
Recommendation · SocialAfter the number exchange, propose a concrete date plan with a specific venue, day, and activity type during the same interaction. Offer flexible date options like getting a bite to eat or a drink or a mocktail when proposing the meetup.
Coach Kyle · How to Talk to Women in Public: Real Infield Breakdown
Recommendation · SocialThe coach critiques the student's 'Have you ever been to Seattle? You could come visit me' after four minutes with no prior flirting as a bit much of a jump. He models a smoother, more playful version: 'You've never been there? Okay, well, you got to come visit me in Seattle and then maybe you could be my host in Russia one day.' Tying a flirty invitation back to something relevant the woman said earlier (like her being from Russia) makes it more fun and smoother.
Coach Kyle · How to Talk to Women in Public: Real Infield Breakdown
Recommendation · SocialAsk what she's up to tonight to learn her availability, ask what she's doing for fun this weekend to set up the idea of hanging out later, and ask whether she's here with friends or by herself to understand her situation.
Coach Kyle · From Hi to Coffee Date (LIVE DEMO)
Recommendation · SocialIf she says she has to meet friends soon but offers to walk with you, accept the partial availability, pivot, and continue the interaction by walking with her.
Coach Kyle · From Hi to Coffee Date (LIVE DEMO)
RecommendationCharlie Guo recommends running 'git clone openai/codex' and then asking Codex about Codex to start building your own applications or integrations immediately, noting the Codex repo is a great reference source for AI engineers.
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
RecommendationCharlie Guo recommends telling the agent in agents.md to use the linter for simple validation, but using hooks for more sophisticated or complicated output validation.
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
RecommendationGabriel Chua recommends running an automation every Friday that reviews all your conversation threads to find skills you could improve, things you could add to the agents Markdown file, and skills you haven't been using that could be removed.
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
RecommendationCharlie Guo recommends setting up automations in the Codex app under the Scheduled page so they spin out in their own thread, useful for one-time looks you archive afterward.
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
RecommendationCharlie Guo recommends setting up an automation to triage Slack, email, and Linear notifications rather than manually checking each source, since manual tracking drowns you in notifications.
Also discussed by Adam Guild on The Official SaaStr Podcast: SaaS | Founders | Investors, Anish Acharya on The a16z Show, The a16z Show (unclassified source — not counted until classified). Not counted as independent sources.
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
RecommendationGabriel Chua recommends cloning the openai/codex repo and asking Codex directly about the Codex AppServer to start building applications or integrations immediately.
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
RecommendationCharlie Guo warns that not checking whether Codex was blocked by missing context or permissions before scaling up compounds broken workflows. He recommends diagnosing blockers first — what context or permissions Codex needed — and then encoding the fix into skills or plugins.
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
Recommendation · MoneyKent advises that when a feature request comes without validation of why it exists, the product engineer should go back to the PM and ask to understand more about why it exists. Asking where a request is coming from helps shape the system used to build it.
AI Engineer · Build the Right Thing: Product Engineering (Part 1) — Kent C. Dodds, EpicProduct.engineer
Recommendation · MoneyKent advises hiring managers not to do coding challenges at all when hiring product engineers — and certainly not ones where candidates are not allowed to use an AI agent. He argues that banning AI agents in coding challenges signals an awful company to work at, because it contradicts what you're actually hiring the engineer to do.
AI Engineer · Build the Right Thing: Product Engineering (Part 1) — Kent C. Dodds, EpicProduct.engineer
Recommendation · SocialDuring the approach, stand about two feet away from her with feet close together, which keeps her comfortable.
Coach Kyle · A Realistic Approach at a Mall (Infield)
Recommendation · MoneySet up a Slack channel or some mechanism to collect all user feedback in one place. Create a feedback channel that aggregates Reddit threads, X, and all social media into one place. You don't have to answer everything in the feedback channel — that's not necessarily your job; the value is seeing where the rough edges and paper cuts are.
Also discussed by Rob Walling on Startups For the Rest of Us (unclassified source — not counted until classified). Not counted as independent sources.
AI Engineer · Build the Right Thing: Product Engineering (Part 2) — Kent C. Dodds, EpicProduct.engineer
Recommendation · MoneyKent C. Dodds advises that performance metrics must be brought up to at least the baseline line before adding new features on top — having performance metrics under the line will be a problem for your product. Measure performance metrics to make sure you're hitting your goals and are at the level you should be. For basic needs, focus on reliability, completeness, and ownership — these you absolutely have to nail and do right.
AI Engineer · Build the Right Thing: Product Engineering (Part 2) — Kent C. Dodds, EpicProduct.engineer