Illustration of a microphone

Calls with Kent C. Dodds.

You call, I'll answer.

Record your call
Listen to the podcasts here
Apple podcastsPocket CastsPocket CastsPocket Casts
SpotifyRSSRSS
Phone sitting on a stool

What's this all about?

The goal of the Call Kent Podcast is to get my answers to your questions. You record your brief question (120 seconds or less) right from your browser. Then I listen to it later and give my response, and through the magic of technology (ffmpeg), our question and answer are stitched together and published to the podcast feed.

I look forward to hearing from you!

Record your call

Calls with Kent C. Dodds Season 2 — 50 episodes

50.Why are you programming in VScode?
07:22
49.Remix: ways around window undefined
05:42
48.Testing a graphical component
03:21
47.Will there be a KCD Trilogy? (Yes)
06:17
46.How do you automate KCD?
12:48
45.Question about testing a reusable component
07:01
44.Full Stack Developers... Why?
07:18
43.Mantine's callback with Remix's ActionFunction
05:21
42.How do you convince your team to use E2E?
05:03
41.Migration from React/Rails hybrid to Remix
10:32
40.Do you have any thoughts on Playwright?
04:30
39.Using cookie/privacy policies on personal websites
06:13
38.Leveling up your career while putting family first
07:02
37.Live loading data with remix
05:28
36.Using VPN during software development
03:38
35.Why is there so much hate regarding React lately?
17:24
34.Decomposing remix component
06:15
33.Jump from mid level to senior react developer
08:04
32.React app doesn't work on IE11
05:47
31.Using userEvent vs fireEvent
05:16
30.useMemo vs React.Memo when it comes to JSX
04:46
29.How to build a committed following
07:13
28.Learning Frontend Architecture
04:11
27.Querying the data in nested routes
06:40
26.Nivo charts issue
06:56
25.i18n and Remix
02:57
24. Tests for accessible error messages
03:39
23.Asserting props.onClick in react-testing-library
05:36
22.CatchBoundary on empty datasets
11:00
21.Remix Anti-patterns
04:34
20.Why Framer Motion for Animations
02:38
19.Lack of experience when problem solving
07:18
18.How to identify which button submits a form
03:30
17.Thinking process when reviewing code
06:33
16.Do you read the React source code?
04:23
15.Isolate FE and BE apps vs Remix Full Stack
03:54
14.Using Remix with a custom backend (Nestjs)
07:26
13.Feedback speed in TDD
04:55
12.Understand what's effect and what is derived state
06:27
11.Order of Courses to Take
05:24
10.State bloating vs api call (again and again)
06:40
09.Separation of rendering vs logics custom hooks
04:47
08.Imposter Syndrome and Working at FAANG
07:03
07.In a Startup only testing in the backend?
04:20
06.Using GraphQL queries in Remix loader functions
03:36
05.Servers + Databases + Remix
05:15
04.I love your website! ITS BEAUTIFUL.
01:38
03.How can I incentivize users to not share accounts?
03:19
02.Could the useState be used without the setter?
06:03
01.Best way to reset a form
05:27
Keywords

react, forms, performance

Description
In the example, submitting the form successfully will still retain the current values of the fields.
I want the behavior such that"
  1. when the server response says the form is NOT submitted successfully, then the form field will have the current values that has been inputted by the user
  2. But when the server response says that the form is successfully submitted, then the form fields will be blank again.
What's do you think is the best and most performant (and readable) code to approach this in pure React? The approach which will reduce the amount of unnecessary rerenders of the fields?
Thank you!
50.Why are you programming in VScode?
07:22
49.Remix: ways around window undefined
05:42
48.Testing a graphical component
03:21
47.Will there be a KCD Trilogy? (Yes)
06:17
46.How do you automate KCD?
12:48
45.Question about testing a reusable component
07:01
44.Full Stack Developers... Why?
07:18
43.Mantine's callback with Remix's ActionFunction
05:21
42.How do you convince your team to use E2E?
05:03
41.Migration from React/Rails hybrid to Remix
10:32
40.Do you have any thoughts on Playwright?
04:30
39.Using cookie/privacy policies on personal websites
06:13
38.Leveling up your career while putting family first
07:02
37.Live loading data with remix
05:28
36.Using VPN during software development
03:38
35.Why is there so much hate regarding React lately?
17:24
34.Decomposing remix component
06:15
33.Jump from mid level to senior react developer
08:04
32.React app doesn't work on IE11
05:47
31.Using userEvent vs fireEvent
05:16
30.useMemo vs React.Memo when it comes to JSX
04:46
29.How to build a committed following
07:13
28.Learning Frontend Architecture
04:11
27.Querying the data in nested routes
06:40
26.Nivo charts issue
06:56
25.i18n and Remix
02:57
24. Tests for accessible error messages
03:39
23.Asserting props.onClick in react-testing-library
05:36
22.CatchBoundary on empty datasets
11:00
21.Remix Anti-patterns
04:34
20.Why Framer Motion for Animations
02:38
19.Lack of experience when problem solving
07:18
18.How to identify which button submits a form
03:30
17.Thinking process when reviewing code
06:33
16.Do you read the React source code?
04:23
15.Isolate FE and BE apps vs Remix Full Stack
03:54
14.Using Remix with a custom backend (Nestjs)
07:26
13.Feedback speed in TDD
04:55
12.Understand what's effect and what is derived state
06:27
11.Order of Courses to Take
05:24
10.State bloating vs api call (again and again)
06:40
09.Separation of rendering vs logics custom hooks
04:47
08.Imposter Syndrome and Working at FAANG
07:03
07.In a Startup only testing in the backend?
04:20
06.Using GraphQL queries in Remix loader functions
03:36
05.Servers + Databases + Remix
05:15
04.I love your website! ITS BEAUTIFUL.
01:38
03.How can I incentivize users to not share accounts?
03:19
02.Could the useState be used without the setter?
06:03
01.Best way to reset a form
05:27
Keywords

react, forms, performance

Description
In the example, submitting the form successfully will still retain the current values of the fields.
I want the behavior such that"
  1. when the server response says the form is NOT submitted successfully, then the form field will have the current values that has been inputted by the user
  2. But when the server response says that the form is successfully submitted, then the form fields will be blank again.
What's do you think is the best and most performant (and readable) code to approach this in pure React? The approach which will reduce the amount of unnecessary rerenders of the fields?
Thank you!
50.Why are you programming in VScode?
07:22
49.Remix: ways around window undefined
05:42
48.Testing a graphical component
03:21
47.Will there be a KCD Trilogy? (Yes)
06:17
46.How do you automate KCD?
12:48
45.Question about testing a reusable component
07:01
44.Full Stack Developers... Why?
07:18
43.Mantine's callback with Remix's ActionFunction
05:21
42.How do you convince your team to use E2E?
05:03
41.Migration from React/Rails hybrid to Remix
10:32
40.Do you have any thoughts on Playwright?
04:30
39.Using cookie/privacy policies on personal websites
06:13
38.Leveling up your career while putting family first
07:02
37.Live loading data with remix
05:28
36.Using VPN during software development
03:38
35.Why is there so much hate regarding React lately?
17:24
34.Decomposing remix component
06:15
33.Jump from mid level to senior react developer
08:04
32.React app doesn't work on IE11
05:47
31.Using userEvent vs fireEvent
05:16
30.useMemo vs React.Memo when it comes to JSX
04:46
29.How to build a committed following
07:13
28.Learning Frontend Architecture
04:11
27.Querying the data in nested routes
06:40
26.Nivo charts issue
06:56
25.i18n and Remix
02:57
24. Tests for accessible error messages
03:39
23.Asserting props.onClick in react-testing-library
05:36
22.CatchBoundary on empty datasets
11:00
21.Remix Anti-patterns
04:34
20.Why Framer Motion for Animations
02:38
19.Lack of experience when problem solving
07:18
18.How to identify which button submits a form
03:30
17.Thinking process when reviewing code
06:33
16.Do you read the React source code?
04:23
15.Isolate FE and BE apps vs Remix Full Stack
03:54
14.Using Remix with a custom backend (Nestjs)
07:26
13.Feedback speed in TDD
04:55
12.Understand what's effect and what is derived state
06:27
11.Order of Courses to Take
05:24
10.State bloating vs api call (again and again)
06:40
09.Separation of rendering vs logics custom hooks
04:47
08.Imposter Syndrome and Working at FAANG
07:03
07.In a Startup only testing in the backend?
04:20
06.Using GraphQL queries in Remix loader functions
03:36
05.Servers + Databases + Remix
05:15
04.I love your website! ITS BEAUTIFUL.
01:38
03.How can I incentivize users to not share accounts?
03:19
02.Could the useState be used without the setter?
06:03
01.Best way to reset a form
05:27
Keywords

react, forms, performance

Description
In the example, submitting the form successfully will still retain the current values of the fields.
I want the behavior such that"
  1. when the server response says the form is NOT submitted successfully, then the form field will have the current values that has been inputted by the user
  2. But when the server response says that the form is successfully submitted, then the form fields will be blank again.
What's do you think is the best and most performant (and readable) code to approach this in pure React? The approach which will reduce the amount of unnecessary rerenders of the fields?
Thank you!
50.Why are you programming in VScode?
07:22
49.Remix: ways around window undefined
05:42
48.Testing a graphical component
03:21
47.Will there be a KCD Trilogy? (Yes)
06:17
46.How do you automate KCD?
12:48
45.Question about testing a reusable component
07:01
44.Full Stack Developers... Why?
07:18
43.Mantine's callback with Remix's ActionFunction
05:21
42.How do you convince your team to use E2E?
05:03
41.Migration from React/Rails hybrid to Remix
10:32
40.Do you have any thoughts on Playwright?
04:30
39.Using cookie/privacy policies on personal websites
06:13
38.Leveling up your career while putting family first
07:02
37.Live loading data with remix
05:28
36.Using VPN during software development
03:38
35.Why is there so much hate regarding React lately?
17:24
34.Decomposing remix component
06:15
33.Jump from mid level to senior react developer
08:04
32.React app doesn't work on IE11
05:47
31.Using userEvent vs fireEvent
05:16
30.useMemo vs React.Memo when it comes to JSX
04:46
29.How to build a committed following
07:13
28.Learning Frontend Architecture
04:11
27.Querying the data in nested routes
06:40
26.Nivo charts issue
06:56
25.i18n and Remix
02:57
24. Tests for accessible error messages
03:39
23.Asserting props.onClick in react-testing-library
05:36
22.CatchBoundary on empty datasets
11:00
21.Remix Anti-patterns
04:34
20.Why Framer Motion for Animations
02:38
19.Lack of experience when problem solving
07:18
18.How to identify which button submits a form
03:30
17.Thinking process when reviewing code
06:33
16.Do you read the React source code?
04:23
15.Isolate FE and BE apps vs Remix Full Stack
03:54
14.Using Remix with a custom backend (Nestjs)
07:26
13.Feedback speed in TDD
04:55
12.Understand what's effect and what is derived state
06:27
11.Order of Courses to Take
05:24
10.State bloating vs api call (again and again)
06:40
09.Separation of rendering vs logics custom hooks
04:47
08.Imposter Syndrome and Working at FAANG
07:03
07.In a Startup only testing in the backend?
04:20
06.Using GraphQL queries in Remix loader functions
03:36
05.Servers + Databases + Remix
05:15
04.I love your website! ITS BEAUTIFUL.
01:38
03.How can I incentivize users to not share accounts?
03:19
02.Could the useState be used without the setter?
06:03
01.Best way to reset a form
05:27
Keywords

react, forms, performance

Description
In the example, submitting the form successfully will still retain the current values of the fields.
I want the behavior such that"
  1. when the server response says the form is NOT submitted successfully, then the form field will have the current values that has been inputted by the user
  2. But when the server response says that the form is successfully submitted, then the form fields will be blank again.
What's do you think is the best and most performant (and readable) code to approach this in pure React? The approach which will reduce the amount of unnecessary rerenders of the fields?
Thank you!

Looking for more content?

Have a look at these articles.

See the full blog
by Mohamed Nohassi
by Mohamed Nohassi
December 1st, 2020 — 3 min read
useEffect vs useLayoutEffect
by rawpixel.com
by rawpixel.com
April 9th, 2018 — 3 min read
Compose Render Props