How to create and expose React Context providers and consumers| kentcdodds.com
How React is all you need to manage your application state| kentcdodds.com
What it is, why it's good, why it's bad, and how to avoid common problems with it| kentcdodds.com
[Guillermo Rauch](https://twitter.com/rauchg) [tweeted](https://twitter.com/rauchg/status/807626710350839808) this a while back. Let's take a dive into what it means.| kentcdodds.com
Tests should help me be confident that my application is working and there are better ways to do that than shallow rendering.| kentcdodds.com
Without using React.memo, PureComponent, or shouldComponentUpdate| kentcdodds.com
TypeScript forces you to acknowledge you can't know what was thrown making getting the error message a pain. Here's how you can manage it.| kentcdodds.com
Testing implementation details is a recipe for disaster. Why is that? And what does it even mean?| kentcdodds.com
When to pass a function to useState and setState| kentcdodds.com
Why you shouldn't mock fetch or your API Client in your tests and what to do instead.| kentcdodds.com
Axios can do a ton of stuff, but here's a simpler solution that can handle most use cases| kentcdodds.com
A simple principle that can drastically improve your reusable code| kentcdodds.com
A fun exercise to help understand the differences and use cases of these two related hooks| kentcdodds.com
Why using hooks like beforeEach as a mechanism for code reuse leads to unmaintainable tests and how to avoid it.| kentcdodds.com
A simple trick to simplify your application and component state| kentcdodds.com
How to start optimizing your React app renders| kentcdodds.com
