Pivot to choosing the path of the person you want to be
Brooks advises that the solution to post-success craving is not to call yourself a horrible human being but to pivot to choosing the path of the person you want to be.
endorsed
42,308 results · Most relevant
Brooks advises that the solution to post-success craving is not to call yourself a horrible human being but to pivot to choosing the path of the person you want to be.
endorsed
Dr. Arthur Brooks recommends that to judge whether a pursuit is an addiction, a compulsion, unhealthy or healthy, you should ask: how tightly am I quantifying every little bit of it and thinking about what I've done?
Adolphs advises stepping back to gain metacognitive oversight over your full spectrum of emotional options, incorporating context, and choosing the most adaptive path; this requires a keen sense of your internal state and of context.
Dr. Fei-Fei Li recommends that teachers and parents are the most important people in society and should be talked to, uplifted, supported, and given resources, so that kids can be helped — hope for kids should not be blind. Andrew Huberman adds that neither doomerism nor utopianism helps teachers; both messages fail them, and if teachers aren't helped, kids aren't helped.
A demonstrated in-season build-up: start with a power clean at 70 kilos for a double off the box, rest about a minute and a half between doubles while building up, hit the second set at 90 kilos (about 200 pounds) for a double right off the box, and build up to about 242 pounds for a good strong single with really good speed. Ramp singles in steps (e.g., 242 to 264 pounds) to progressively load the nervous system, resting longer after heavier ramp singles. A week out from the season starting, don't go crazy with training intensity.
Structure a power clean workout by ramping to a heavy single to establish a ceiling before dropping back down for drop sets. After ramping to the ceiling, perform a drop set at around 76% of the established max doing full cleans for a set of two, then do two or three sets of doubles at full range on the cleans. After a heavy impulse-based power clean, use the drop set to transition into mobility work.
After she says thanks, come back with 'yeah, you just have like a very interesting look' to prompt elaboration. If she doesn't elaborate, you may need to talk more and ask another question. Going into the topic she reveals (e.g., her tattoos) is what extends the interaction past 15 seconds.
endorsed
Hormozi advises selling to clients near the 12-month mark of their engagement while the pain is still elevated, and specifically when the buyer is mid-decision ('in flight') rather than making a new decision. He frames this as 'let's just keep the party going' rather than starting something new.
Hormozi tells Hussey not to buy additional locations until the existing practice's problems are fixed — there's no point adding another practice when he doesn't yet know how to run one without his dad. Fixing the existing practice must happen before any conversations about buying locations can occur.
The host recommends using every form of leverage that you have at your disposal to solve the constraint of the business, warning that if you don't know what the constraint of the business is, just doing more automated work does not make you more money.
The host says the highest leverage thing you can do, even higher leverage than AI, is making good decisions. He recommends determining that something is not a priority rather than automating something that is not a priority, noting that telling your team you're not doing a whole bunch of work because it's not important anymore gets much more out of the team. He warns that automating a low-priority task just creates an irrelevant output, whereas cutting it frees team capacity.
The host recommends using an event-based marketing motion where the only required action is outreach, eliminating the need for ad assembly.
Mahmoud Abdelwahab argues that the final and most important step when building internal tools with agents is verification, and that a verification loop makes a dramatic ('night and day') difference in output quality.
Clone the workshop repo, cd into the research desk directory, run npm install or bun install, then spin up the server with bun run dev. The first prerequisite step is copying .env.example into .env.local.
A demo shows the basic agent creation flow: prompt Claude with 'build me an agent that tells me jokes every time given a topic' and hit enter; Claude generates the system prompt, name, description, and model. Give the agent access to the agent tool set, then hit create agent, which calls the v1 agents endpoint. Configure the environment (the template for the sandbox) by creating a new one, choose packages to install, then start the session and test run it with a prompt like 'Tell me jokes about cats'.
Type 'workshop next' to have Claude implement the provisioning scheme to upgrade the agent with sub-agents and an SEC skill. There should be a button in the setup that says 'staff to desk' — when clicked, it runs the provisioning. You can also delete the skill and ask Claude to reprovision it so it recreates all the resources, including the sub-agents, the skill, and a memory store.
Give the agent a skill that lets it talk to the SEC, describing how to use the Python package and that it has to use the Edgar identity to call. The SEC requires you to provide your name and email when calling their API so they know who's calling; put your Edgar identifier (name and email) into .env.local.
Use a memory store that allows sharing knowledge across sessions, so agents can reuse what was learned previously.
In the demo UI, type 'build me an agent that tells me jokes every time given a topic' and hit enter. Claude automatically generates a system prompt, name, description, and model choice; you can change the model before creating. Then give the agent access to the agent tool set and hit create agent, which calls the v1 agents endpoint.
Buy, don't build, when a third-party product can do the job — even if you've already built your own version. If a vendor could have delivered the same capability in an hour, buy it instead of building — but only if you evaluate the vendor before building. Before building an internal agent, check whether the vendor supports your full stack — quirky integrations (QuickBooks, Bill.com, PandaDocs, Canadian entities) are a common reason third-party products won't work. A third-party agent built by a strong team is less likely to catastrophically break your application than your own vibe-coded build. Vibe coding your own CRM is moronic — don't build your own CRM even though edge cases sometimes justify building.
Choose sources → to get a library of your own and a daily brief.