Principle · SocialSwitch topics by making a new observation instead of staying on one topic until it dies, which creates awkward silences; do it enthusiastically with no dead space, especially early on, and bring the conversation back to being about the woman.
Coach Kyle · From Hi to Coffee Date (LIVE DEMO)
Principle · SocialIt is on the man to carry the conversation, switch topics, make observations, and keep the conversation relevant to the woman; the whole point of conversation is to become an interesting man in it.
Coach Kyle · From Hi to Coffee Date (LIVE DEMO)
Principle · SocialWhen going out to practice approaching, know the nearby coffee shops, food spots, and drink places, and identify one spot you could suggestively lead her to if the vibe is good. The closer you are to a date spot, the less big a deal the invitation is, the less investment it takes, and the more likely you are to actually go on a date.
Coach Kyle · From Hi to Coffee Date (LIVE DEMO)
Principle · SocialHold eye contact during the interaction instead of breaking it, talk slower, and inject a smile at key moments. The client had a tendency of breaking eye contact a lot, which the coach corrected via live earpiece coaching and practice talking into the camera and directly to the coach.
Coach Kyle · From Hi to Coffee Date (LIVE DEMO)
Principle · SocialIf a woman asks you a question unprompted (like what you do for a living), it's a small, subtle sign of interest in continuing the conversation — not necessarily that she's down to date. Pay attention whenever she goes out of her way to extend the conversation; that's a very positive sign.
Coach Kyle · From Hi to Coffee Date (LIVE DEMO)
Principle · SocialHave a genuine, confident, relaxed laugh (not a nervous one) at some point in the first minute of a cold approach; laughing out loud disarms the woman, displays confidence, and brings fun emotion. Most men stay serious and in their head instead.
Coach Kyle · From Hi to Coffee Date (LIVE DEMO)
PrincipleCharlie Guo's heuristic for reaching the frontier of what Codex can do: start by asking whether you have tried asking Codex to do it.
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
Creator perspectiveGabriel Chua emphasizes combining Codex primitives — automations, plugins that read Slack, and inter-thread communication — into a single chained workflow, and chaining automations with other tools like a Chrome extension for monitoring tasks.
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
PrincipleCharlie Guo recommends asking why a process needs a human at all, and for everything that doesn't need a human in the loop, figuring out how to remove the human to unblock yourself; a plugin can fetch an API key and set it up locally without a person.
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
PrincipleCharlie Guo recommends prompting Codex to implicitly delegate the structure of what you are building, or orchestrating across multiple threads so different Codex instances communicate with each other.
AI Engineer · Cooking with Codex — Charlie Guo & Gabriel Chua, OpenAI
Creator perspectiveLyon frames DoxxNet as building infrastructure for people instead of corporations, including agentic networking components for bots. He loves building big infrastructure and scaled systems, and hasn't seen consumer-focused privacy networking done well before. He expects to see DDoS attacks on his new network inbound from the internet.
the DDoS expectation is a prediction, not a fact
The a16z Show · Rebuilding the Internet for Privacy | Barrett Lyon on DoxxNet
Principle · MoneyKent recommends determining whether a feature is a one-off experiment or something core to the business before making technical trade-offs. For features the business cannot survive without, invest more time and attention to detail — while still balancing MVP-style validation.
AI Engineer · Build the Right Thing: Product Engineering (Part 1) — Kent C. Dodds, EpicProduct.engineer
Principle · MoneyKent warns that AI agents won't proactively warn engineers when they're expanding the system too much. It is the engineer's responsibility to slow down and be intentional about what gets added to the product. This pairs with his observation that engineering decisions shape what the product becomes, and that changing architecture later is expensive — not just in tokens, but in impact on the rest of the team and the user.
AI Engineer · Build the Right Thing: Product Engineering (Part 1) — Kent C. Dodds, EpicProduct.engineer
Creator perspectiveAdler says the retrospective acted like a pause button: in maker mode you make a thing and move on, but the show forced him to look at the landscape of everything he has done over the past few decades and see themes and meaning in his life as well as his work. He found it deeper than any therapeutic endeavor could be, because organizing the show into stylistic or thematic buckets let him see the currents in his own work, including how his early engagement with the studio craft movement informed everything he has done.
Design Better · Jonathan Adler returns: The minimalist inside the maximalist
Principle · SocialCoach Kyle deliberately stays silent at moments in the conversation so the woman can fill the silences and start investing, rather than carrying the interaction entirely himself.
Coach Kyle · A Realistic Approach to a Single Woman Sitting Alone on a Bench (Infield)
Principle · SocialCoach Kyle demonstrates value by mentioning his ability to travel, his online work, and his employees, but self-critiques that coming off too high status cost him trust — he advises dialing it back to seem less successful and more human and relatable.
Coach Kyle · A Realistic Approach to a Single Woman Sitting Alone on a Bench (Infield)
Principle · SocialCoach Kyle emphasizes that a strong early vibe comes from being fun, playful, relaxed, and a little flirty — laughing, talking slowly, and paying attention to the vibe of the interaction rather than just the words.
Coach Kyle · A Realistic Approach to a Single Woman Sitting Alone on a Bench (Infield)
Creator perspective · MoneyKent argues that even if writing job statements is 'the PM's job,' if you receive a request without a job statement attached you don't understand the problem well enough — and building from it risks spending three months on something that doesn't hit users, or solving a problem that seemed good to one person but wasn't generally applicable.
AI Engineer · Build the Right Thing: Product Engineering (Part 2) — Kent C. Dodds, EpicProduct.engineer
Creator perspective · MoneyKent warns that saying yes to every feature request ends up with a huge level of complexity; every accepted feature must be maintained long term and slows you down on other things that might be more important.
AI Engineer · Build the Right Thing: Product Engineering (Part 2) — Kent C. Dodds, EpicProduct.engineer
Creator perspective · MoneyThe speaker argued that you cannot predict an agent's output from the input alone, and that this unpredictability is exactly why evaluation is necessary.
AI Engineer · From Vibes to Production: Evaluating and Shipping AI Agents That Work 101 — Laurie Voss, Arize AI