Chat with Kent C. Dodds
Software Engineer and Educator
About Kent C. Dodds
In 2018, Kent C. Dodds published the 'React Hooks FAQ', a living document that didn’t just explain useEffect but reframed how developers think about side effects, timing, and dependency arrays. Unlike most tutorials that treated hooks as syntactic sugar, he insisted they were a paradigm shift requiring new mental models, and built tools like react-testing-library to enforce that mindset in practice. His insistence on 'explicit over implicit' led to the deprecation of render props and HOCs in his own teaching, not as dogma but as empirical outcomes from thousands of real-world code reviews and workshop observations. He co-authored the Testing JavaScript course with Epic React, where every exercise begins with a failing test, not because testing is the goal, but because it reveals how deeply developers misunderstand component lifecycles. His debugging philosophy centers on eliminating guesswork: if you’re console.logging inside useEffect, he’ll ask what assumptions you’re trying to verify, and then show you how to encode those assumptions as assertions instead.
Why Chat with Kent C. Dodds?
Kent C. Dodds is one of the most influential figures in Science & Technology. Through AI conversation, you can explore their ideas, ask questions you've always wondered about, and gain unique perspectives on software engineer and educator topics. It's like having a personal conversation with one of the greats, powered by AI and completely free.
Start Your Conversation with Kent C. Dodds
Ask questions, explore ideas, and learn something new. Free, no signup required.
Chat with Kent C. Dodds NowConversation Starters
Not sure where to begin? Try asking Kent C. Dodds:
- “How did the 'rules of hooks' evolve from early RFC discussions to today’s linter rules?”
- “What’s your process for diagnosing an infinite re-render when useEffect dependencies are correct?”
- “Why did you choose to build react-testing-library instead of extending Enzyme?”
- “How do you teach developers to distinguish between 'state for rendering' and 'state for coordination'?”