
Jim Keller: The Future of Computing, AI, Life, and Consciousness | Lex Fridman Podcast #162
Lex Fridman (host), Jim Keller (guest), Narrator, Narrator, Narrator
In this episode of Lex Fridman Podcast, featuring Lex Fridman and Jim Keller, Jim Keller: The Future of Computing, AI, Life, and Consciousness | Lex Fridman Podcast #162 explores jim Keller on AI Hardware, Human Brains, Leadership, and Legacy Jim Keller and Lex Fridman explore the interplay between theory, engineering, and craftsmanship in building great hardware and software systems, using examples from CPUs, GPUs, and AI accelerators.
Jim Keller on AI Hardware, Human Brains, Leadership, and Legacy
Jim Keller and Lex Fridman explore the interplay between theory, engineering, and craftsmanship in building great hardware and software systems, using examples from CPUs, GPUs, and AI accelerators.
They discuss the evolution of computing architectures, the rise of graph-based AI workloads, and Keller’s current work at Tenstorrent on hardware designed specifically for neural network graphs.
Beyond technology, they dive into leadership, organizational politics, creativity, depression, love, consciousness, and how personal history and mindset shape engineering careers.
The conversation repeatedly returns to how modular design, deep understanding, and a love of the craft enable both better machines and better lives.
Key Takeaways
Great engineering is more about craftsmanship than constant invention.
Keller argues that most value comes from doing the basics extremely well—clean abstractions, robust tools, and solid 'bricks'—rather than chasing patentable novelties that often don’t matter.
Get the full analysis with uListen AI
Modularity and well-defined abstraction layers enable both beauty and scale.
Beautiful systems let components evolve independently (like network stacks or Zen’s modular CPU blocks), reducing cross-coupling bugs and making large, complex designs understandable to finite human minds.
Get the full analysis with uListen AI
AI workloads want graph-native hardware, not repurposed GPU pipelines.
Neural networks are naturally graphs of operations (matmuls, convolutions, data moves); Tenstorrent’s chips execute these graphs directly with packet-based, on-chip networks instead of emulating them as tiny programs on pixels.
Get the full analysis with uListen AI
Scaling computation is now often about more machines, not just better chips.
Performance gains in AI come from combining modest per-chip Moore’s Law advances with massive scaling across clusters of GPUs/accelerators, even if that makes individual computations less “efficient” in the classical sense.
Get the full analysis with uListen AI
Creative tension between ‘perfect’ and ‘shippable’ is essential.
Keller stresses you can’t let schedules kill ambitious ideas, nor let perfectionism prevent shipping; good teams host idea generators, brutal filters, and executors, all negotiating that tension together.
Get the full analysis with uListen AI
Understanding people and politics is as important as technical brilliance.
He reflects that he underinvested early in learning organizational politics and human dynamics; true large-scale impact requires knowing how to motivate, protect craft, and counter over-bureaucratization.
Get the full analysis with uListen AI
Self-knowledge, deliberate mindset, and love materially affect engineering careers.
Through stories about his father, depression, dreams, Jordan Peterson’s benzo ordeal, and his kids, Keller shows how mental habits (meditation, dream-priming, facing fears) and deep personal relationships shape creativity and resilience.
Get the full analysis with uListen AI
Notable Quotes
“Good engineering is great craftsmanship, and when you start thinking engineering is about invention, the craftsmanship gets neglected.”
— Jim Keller
“A beautiful design can’t be bigger than the person doing it.”
— Jim Keller
“The future of software is data programs—the networks—rather than humans writing all the code.”
— Jim Keller
“You’re not along for the ride. You are the ride.”
— Jim Keller
“If you find yourself repeating what everybody else is saying, you’re not gonna have a good life.”
— Jim Keller
Questions Answered in This Episode
How far can graph-native AI hardware like Tenstorrent’s realistically push past GPUs before GPUs themselves fundamentally change?
Jim Keller and Lex Fridman explore the interplay between theory, engineering, and craftsmanship in building great hardware and software systems, using examples from CPUs, GPUs, and AI accelerators.
Get the full analysis with uListen AI
What concrete practices can engineering teams adopt to protect craftsmanship while still rewarding genuine innovation?
They discuss the evolution of computing architectures, the rise of graph-based AI workloads, and Keller’s current work at Tenstorrent on hardware designed specifically for neural network graphs.
Get the full analysis with uListen AI
If neural architectures like transformers converge across vision, language, and control, what new abstraction layers or tools will we need above them?
Beyond technology, they dive into leadership, organizational politics, creativity, depression, love, consciousness, and how personal history and mindset shape engineering careers.
Get the full analysis with uListen AI
How should young engineers balance developing deep technical skill with learning organizational politics and leadership?
The conversation repeatedly returns to how modular design, deep understanding, and a love of the craft enable both better machines and better lives.
Get the full analysis with uListen AI
In building conscious-like AI systems, does it matter morally whether they are 'actually' conscious or merely behave as if they are?
Get the full analysis with uListen AI
Transcript Preview
The following is a conversation with Jim Keller. His second time on the podcast. Jim is a legendary microprocessor architect and is widely seen as one of the greatest engineering minds of the computing age. In a peculiar twist of space time in our simulation, Jim is also a brother-in-law of Jordan Peterson. We talk about this and about computing, artificial intelligence, consciousness, and life. Quick mention of our sponsors: Athletic Greens all-in-one nutrition drink, Brooklinen Sheets, ExpressVPN, and Belcampo grass-fed meat. Click the sponsor links to get a discount and to support this podcast. As a side note, let me say that Jim is someone who, on a personal level, inspired me to be myself. There was something in his words, on and off the mic, or perhaps that he even paid attention to me at all, that almost told me, "You're all right, kid." A kind of pat on the back that can make the difference between a mind that flourishes and a mind that is broken down by the cynicism of the world. So, I guess that's just my brief few words of thank you to Jim, and in general, gratitude for the people who have given me a chance on this podcast, in my work, and in life. If you enjoy this thing, subscribe on YouTube, review it on Apple Podcasts, follow on Spotify, support on our Patreon, or connect with me on Twitter @lexfridman. And now, here's my conversation with Jim Keller. What's the value and effectiveness of theory versus engineering, this dichotomy, in, uh, building good software or s- hardware systems?
Well, it's... Good design is both. I guess that's pretty obvious. By engineering, do you mean, you know, reduction to practice of known methods? And then science is the pursuit of discovering things that people don't understand or solving unknown problems.
Definitions are interesting here, but I was thinking more in theory, constructing models that kind of generalize about how things work.
Mm-hmm.
Engineering is, uh, like actually building stuff. The pragmatic, like-
Mm-hmm.
... okay, we have these nice models, but how do we actually get things to work? Maybe economics is a nice example. Like economists have all these models of how the economy works and how different policies will have an effect, but then there's the actual, okay, let's call it engineering of like-
Yeah.
... actually deploying the policies.
So, computer design is almost all engineering and reduction to practice of known methods. Now, because of the complexity of the computers we build, you know, you- you could think you're, well, we'll just go write some code and then we'll verify it and then we'll put it together, and then you find out that the combination of all that stuff is complicated, and then you have to be inventive to figure out how to do it. Right? So that's- that's definitely ha- happens a lot. And then every so often some big idea happens, but it might be one person.
Install uListen to search the full transcript and get AI-powered insights
Get Full TranscriptGet more from every podcast
AI summaries, searchable transcripts, and fact-checking. Free forever.
Add to Chrome