Show content
Listen to the audio, watch the video, or check out the Show Notes for a summary, key takeaways, and links to people, content, and tools we mention.
Audio
Listen on Spotify:
Listen on Apple Podcasts:
Listen on Substack:
Video
Summary
If you haven’t had an AI epiphany yet, you need to. For many of us, it is a visceral experience achieving something that was hard to imagine doing previously, but the danger is in the extrapolation: will this cause massive job loss? Can I do any kind of work now? Will work be necessary?
The right response is asking hard questions about AI:
Is this the most transformative technology in history?
What are the good things that can come from AI?
What are the bad things that can come from it?
Even if the questions don’t have a clear answer, they beg critical thought about AI, which is the entire point. But we also need to ask questions about ourselves:
Do I tend to overestimate or underestimate AI?
What kind of future do I envision with AI?
How do my answers to those questions influence how I use AI?
Key takeaways
If you haven’t had an AI epiphany, you should: AI is transformative, and the best way to understand the power is to experience it for yourself.
Look back to look forward: We have seen transformative technology before in the form of electricity and the internet. We learn by asking how AI is different, and how it is the same.
Decide on the future you want: Even if you can’t control what the major labs do, you can and should decide what you want the future with AI to look like, and use it accordingly.
Notable mentions and links
Eric described using Cursor to move his 13-year WordPress blog to Next.js on Vercel. It was a project he had put off for years, then it became his first AI epiphany moment.
John mentioned that AI tools delivered through iMessage feel easier to use because they show up in a familiar conversation, even when the underlying features aren’t much different.
John talked about moving years of notes from Evernote to Obsidian with AI after earlier attempts got bogged down in exports and edge cases.
Eric described how he and John used DaVinci Resolve Studio and a Model Context Protocol server to rebuild the show’s intro and editing workflow, create a shorts format, and dial in their audio.