35,595 results · Most relevant
Eugene Teo describes his complete long-form video production workflow: create one long-form idea first, script every line, organize scripts in a multi-column table with B-roll and intended results, review for redundancy, then extract 5-10 short-form pieces to push across social platforms.
The proposed alternative is an application-specific passive device where the physics of light propagation performs a step of the diffusion procedure; by iterating on the optical system architecture, one can start from a random distribution of pixels and, just by letting the physics do its work, create new samples from the desired dataset.
Hormozi's core recommendation: if you want to get more buyers from your content, you have to make videos for your buyers.
resolved
Letting the shoulder position drift forward on dips puts a lot of stress on the anterior shoulder capsule. As the descent goes deeper, the shoulder gets pitched more and more forward, giving excess stress to the structures inside the shoulder joint.
The upright row puts the shoulder into an internally rotated position by having the elbow higher than the wrist, and adding load further drives the aggravation, ultimately causing impingement and rotator cuff inflammation. The creator says the upright row is a bad exercise not worth fixing and is not worth saving, especially for long-term shoulder health.
Steve Toth describes that sharing knowledge publicly and consistently (notably on LinkedIn) led people to eventually contact him, and that sharing a specific win publicly generated same-day inbound hiring interest.
Steve Toth recommends banking up money before going freelance, because a nest egg protects you from failure and lets you quote clients your higher number without fear. The narrator adds that Toth's nest egg and confidence let him value himself more and win higher-paying clients.
With Bill, Theo tried to create intimacy immediately; with Mike, he let it build incrementally. Choosing when to share something can either deepen the conversation or kill it completely. You know you've shared the right amount when the conversation keeps going versus getting shut down.
By repeating what Mike said back to him or paraphrasing it, Theo makes Mike feel like he's not only being heard, he's being understood. In Theo's case, reflective listening helps him stay present in the conversation and focus on Mike rather than on himself.
The narrator describes two complementary moves: zooming out a level when a conversation gets too intense takes the pressure off without shutting the topic down (as when Theo asked to go back to the quarters), and zooming in gradually — asking a more personal question only after the person has engaged with wider topics, watching their body language for passion — is how Theo and Mike got to a deep place early.
Sean builds rapport with Will through sharing vulnerability himself. When we share something vulnerable with someone, we're usually looking for a particular response, whether it's validation or reassurance or empathy. Modeling positive vulnerability for someone like Will is one of the most generous things you can do in a relationship, but it's also dangerous. If you want to practice sharing vulnerability, share something that you're comfortable getting nothing back from. If you need someone else to reassure you or open up in return or respond a certain way, you're putting your emotional state in their hands, which can make it much harder to stay grounded. Sean can respond calmly to Will's insensitive remark because he didn't start talking about his wife looking for something from Will.
When someone provokes you, it's nearly impossible to not react in the moment — that's outside of your control. What is in your control is taking time to process things after the fact. After someone gets under your skin, go home and process what just happened. Processing not only helps you make sense of it, it also increases your empathy for the other person. Grounded charisma comes from slowing down and looking for the underlying pattern, then figuring out what the actual conflict is instead of just reacting to what seemed to happen on the surface.
Use LLMs to help generate plans, but keep the plans themselves deterministic and explainable to the customer — especially for recovery scenarios. Never use a probabilistic mechanism for data recovery in a cyber scenario, because you cannot afford to guess.
Charlie Guo warns that giving a Goal vague or non-verifiable completion criteria leads the model to technically complete the task but not in the way you expected; be really specific with the criteria.
Gabriel Chua advises against pasting sensitive credentials like deployment keys directly into chat — ask Codex for a secure way to set them instead — and warns that failing to provide credentials or permissions for external services like Vercel and Convex blocks the agent's critical path and stalls the whole task.
Gabriel Chua recommends chaining Codex primitives — automations, plugins, inter-thread communication, and work tree threads — together when you want to build a software factory, a system that builds individual pieces of software on an assembly line rather than a single piece of software.
Charlie Guo explains that Codex hooks are configured via config.toml in the Codex home directory, and recommends using them to introduce deterministic behavior at checkpoints: logging conversations, scanning inputs/outputs for security (e.g., detecting pasted API keys), checking tool calls against an approved whitelist, and running custom validation checks when a turn stops.
The FBI built a secure messaging app and marketed it exclusively to organized criminal groups (Operation Trojan Shield / ANOM), leading to arrests in Australia and the US, with most of those criminals indicted and imprisoned. The host uses this as the most illustrative story about creepy VPNs, noting that VPNs and secure messaging tools can be compromised by the very entities that market them as safe — and that free VPNs on app stores are similarly suspect ('if it's free, there's nothing free').
Kent C. Dodds's central thesis: since AI agents make implementation easy, the scarce, valuable skill shifts to deciding what to build and whether it is worth building. He notes the entire workshop depends on this slide.
Kent C. Dodds warns that when people get an idea, they tend to jump straight into over-specifying the solution — mobile app, website, integrations — before the potential user has even agreed the problem is worth solving. He endorses validating the problem with users first, before committing to a specific solution shape.
Choose sources → to get a library of your own and a daily brief.