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 4 — 49 episodes

49.How to keep Type-Safety when defering data from a Remix loader
04:21
48.Good open source projects implementing frontend testing strategy
03:43
47.Should I learn GraphQL or just stick with REST?
02:50
46.React Components vs Progressive Enhancement
04:32
45.Test Cleanup: in the test or in afterEach
07:40
44.How many hours do you spend coding?
05:16
43.Remix Vite: Debugging Production issues
04:14
42.Inspired by Your Work
06:23
41.When to add a CSP (Content Security Policy)
05:21
40.Do generated types from OpenAPI spec change testing?
06:50
39.Prevent revalidation of remix loaders after mutation
04:05
38.Design the React component library
04:47
37.SEO Optimization and Hosting
08:18
36.Progress bar for mutations in Remix
09:13
35.Mocking in the full stack metaframework Era
10:14
34.How do you create advanced content for developers
09:54
33.A Button Per form or One Form with Multiple Buttons
04:50
32.Toasts in Remix
06:38
31.Unpaid internships and indentured servitude
04:56
30.It's fine to re-render
09:56
29.Data Structures and Algorithms
04:26
28.Remix Flat Routes vs Remix v2 Router
05:26
27.Generating CSS with Remix Resource Routes
04:52
26.Using Downshift with Conform to manage an input
06:22
25.Jake Lazaroff’s article on Web Components
07:49
24.Code Organization in Full Stack Apps
04:17
23.Client Hints and profiling
04:21
22.Building and Testing an MDX-based Blog
06:58
21.EpicWeb.dev is now available!
02:30
20.What is full stack for EpicWeb.dev?
03:10
19.Improving as a software engineer
06:25
18.Why didn't you break root.tsx into smaller components?
03:10
17.Am I stuck in tutorial heck?
06:37
16.Scaling Epic-Stack in a single region
05:09
15.React Lazy initializers Call Order
02:39
14.How do you approach major project updates
07:16
13.Organizing your first workshop
28:27
12.Conform sets novalidate & validation attributes?
04:36
11.My skill stuck at current job, should I quit?
07:20
10.How do you host your videos?
03:57
09.How are you still productive!?
07:35
08.Best practice for using localStorage in React
09:20
07.Remix Full-Stack Components (vs Server Components)
07:44
06.A 10 year old itch to make a switch (QA to dev)
11:52
05.Should I go to college or not?
09:47
04.Resources to learn senior development skills
07:37
03.Passing state across components in RemixJS
06:48
02.How To Deal with Hiring Developers?
10:06
Keywords

hiring, javascript, developers

Description
I have to manage my projects and outsource them, otherwise, I would never make enough money to keep my business afloat. I have this problem, where, when I start a project, the product owner will ask questions like, "What happens if you die?" and my best answer to that is, "That's why we have employees". But, when I go to hire employees, sometimes they completely just ignore the stack that I'm using and they go off and do their own thing, which becomes difficult to manage. Should I be ruling with an iron fist, or should I just be more of a liason between my clients and my developers?
01.Why do you use the Express adapter for your app?
03:21
49.How to keep Type-Safety when defering data from a Remix loader
04:21
48.Good open source projects implementing frontend testing strategy
03:43
47.Should I learn GraphQL or just stick with REST?
02:50
46.React Components vs Progressive Enhancement
04:32
45.Test Cleanup: in the test or in afterEach
07:40
44.How many hours do you spend coding?
05:16
43.Remix Vite: Debugging Production issues
04:14
42.Inspired by Your Work
06:23
41.When to add a CSP (Content Security Policy)
05:21
40.Do generated types from OpenAPI spec change testing?
06:50
39.Prevent revalidation of remix loaders after mutation
04:05
38.Design the React component library
04:47
37.SEO Optimization and Hosting
08:18
36.Progress bar for mutations in Remix
09:13
35.Mocking in the full stack metaframework Era
10:14
34.How do you create advanced content for developers
09:54
33.A Button Per form or One Form with Multiple Buttons
04:50
32.Toasts in Remix
06:38
31.Unpaid internships and indentured servitude
04:56
30.It's fine to re-render
09:56
29.Data Structures and Algorithms
04:26
28.Remix Flat Routes vs Remix v2 Router
05:26
27.Generating CSS with Remix Resource Routes
04:52
26.Using Downshift with Conform to manage an input
06:22
25.Jake Lazaroff’s article on Web Components
07:49
24.Code Organization in Full Stack Apps
04:17
23.Client Hints and profiling
04:21
22.Building and Testing an MDX-based Blog
06:58
21.EpicWeb.dev is now available!
02:30
20.What is full stack for EpicWeb.dev?
03:10
19.Improving as a software engineer
06:25
18.Why didn't you break root.tsx into smaller components?
03:10
17.Am I stuck in tutorial heck?
06:37
16.Scaling Epic-Stack in a single region
05:09
15.React Lazy initializers Call Order
02:39
14.How do you approach major project updates
07:16
13.Organizing your first workshop
28:27
12.Conform sets novalidate & validation attributes?
04:36
11.My skill stuck at current job, should I quit?
07:20
10.How do you host your videos?
03:57
09.How are you still productive!?
07:35
08.Best practice for using localStorage in React
09:20
07.Remix Full-Stack Components (vs Server Components)
07:44
06.A 10 year old itch to make a switch (QA to dev)
11:52
05.Should I go to college or not?
09:47
04.Resources to learn senior development skills
07:37
03.Passing state across components in RemixJS
06:48
02.How To Deal with Hiring Developers?
10:06
Keywords

hiring, javascript, developers

Description
I have to manage my projects and outsource them, otherwise, I would never make enough money to keep my business afloat. I have this problem, where, when I start a project, the product owner will ask questions like, "What happens if you die?" and my best answer to that is, "That's why we have employees". But, when I go to hire employees, sometimes they completely just ignore the stack that I'm using and they go off and do their own thing, which becomes difficult to manage. Should I be ruling with an iron fist, or should I just be more of a liason between my clients and my developers?
01.Why do you use the Express adapter for your app?
03:21
49.How to keep Type-Safety when defering data from a Remix loader
04:21
48.Good open source projects implementing frontend testing strategy
03:43
47.Should I learn GraphQL or just stick with REST?
02:50
46.React Components vs Progressive Enhancement
04:32
45.Test Cleanup: in the test or in afterEach
07:40
44.How many hours do you spend coding?
05:16
43.Remix Vite: Debugging Production issues
04:14
42.Inspired by Your Work
06:23
41.When to add a CSP (Content Security Policy)
05:21
40.Do generated types from OpenAPI spec change testing?
06:50
39.Prevent revalidation of remix loaders after mutation
04:05
38.Design the React component library
04:47
37.SEO Optimization and Hosting
08:18
36.Progress bar for mutations in Remix
09:13
35.Mocking in the full stack metaframework Era
10:14
34.How do you create advanced content for developers
09:54
33.A Button Per form or One Form with Multiple Buttons
04:50
32.Toasts in Remix
06:38
31.Unpaid internships and indentured servitude
04:56
30.It's fine to re-render
09:56
29.Data Structures and Algorithms
04:26
28.Remix Flat Routes vs Remix v2 Router
05:26
27.Generating CSS with Remix Resource Routes
04:52
26.Using Downshift with Conform to manage an input
06:22
25.Jake Lazaroff’s article on Web Components
07:49
24.Code Organization in Full Stack Apps
04:17
23.Client Hints and profiling
04:21
22.Building and Testing an MDX-based Blog
06:58
21.EpicWeb.dev is now available!
02:30
20.What is full stack for EpicWeb.dev?
03:10
19.Improving as a software engineer
06:25
18.Why didn't you break root.tsx into smaller components?
03:10
17.Am I stuck in tutorial heck?
06:37
16.Scaling Epic-Stack in a single region
05:09
15.React Lazy initializers Call Order
02:39
14.How do you approach major project updates
07:16
13.Organizing your first workshop
28:27
12.Conform sets novalidate & validation attributes?
04:36
11.My skill stuck at current job, should I quit?
07:20
10.How do you host your videos?
03:57
09.How are you still productive!?
07:35
08.Best practice for using localStorage in React
09:20
07.Remix Full-Stack Components (vs Server Components)
07:44
06.A 10 year old itch to make a switch (QA to dev)
11:52
05.Should I go to college or not?
09:47
04.Resources to learn senior development skills
07:37
03.Passing state across components in RemixJS
06:48
02.How To Deal with Hiring Developers?
10:06
Keywords

hiring, javascript, developers

Description
I have to manage my projects and outsource them, otherwise, I would never make enough money to keep my business afloat. I have this problem, where, when I start a project, the product owner will ask questions like, "What happens if you die?" and my best answer to that is, "That's why we have employees". But, when I go to hire employees, sometimes they completely just ignore the stack that I'm using and they go off and do their own thing, which becomes difficult to manage. Should I be ruling with an iron fist, or should I just be more of a liason between my clients and my developers?
01.Why do you use the Express adapter for your app?
03:21
49.How to keep Type-Safety when defering data from a Remix loader
04:21
48.Good open source projects implementing frontend testing strategy
03:43
47.Should I learn GraphQL or just stick with REST?
02:50
46.React Components vs Progressive Enhancement
04:32
45.Test Cleanup: in the test or in afterEach
07:40
44.How many hours do you spend coding?
05:16
43.Remix Vite: Debugging Production issues
04:14
42.Inspired by Your Work
06:23
41.When to add a CSP (Content Security Policy)
05:21
40.Do generated types from OpenAPI spec change testing?
06:50
39.Prevent revalidation of remix loaders after mutation
04:05
38.Design the React component library
04:47
37.SEO Optimization and Hosting
08:18
36.Progress bar for mutations in Remix
09:13
35.Mocking in the full stack metaframework Era
10:14
34.How do you create advanced content for developers
09:54
33.A Button Per form or One Form with Multiple Buttons
04:50
32.Toasts in Remix
06:38
31.Unpaid internships and indentured servitude
04:56
30.It's fine to re-render
09:56
29.Data Structures and Algorithms
04:26
28.Remix Flat Routes vs Remix v2 Router
05:26
27.Generating CSS with Remix Resource Routes
04:52
26.Using Downshift with Conform to manage an input
06:22
25.Jake Lazaroff’s article on Web Components
07:49
24.Code Organization in Full Stack Apps
04:17
23.Client Hints and profiling
04:21
22.Building and Testing an MDX-based Blog
06:58
21.EpicWeb.dev is now available!
02:30
20.What is full stack for EpicWeb.dev?
03:10
19.Improving as a software engineer
06:25
18.Why didn't you break root.tsx into smaller components?
03:10
17.Am I stuck in tutorial heck?
06:37
16.Scaling Epic-Stack in a single region
05:09
15.React Lazy initializers Call Order
02:39
14.How do you approach major project updates
07:16
13.Organizing your first workshop
28:27
12.Conform sets novalidate & validation attributes?
04:36
11.My skill stuck at current job, should I quit?
07:20
10.How do you host your videos?
03:57
09.How are you still productive!?
07:35
08.Best practice for using localStorage in React
09:20
07.Remix Full-Stack Components (vs Server Components)
07:44
06.A 10 year old itch to make a switch (QA to dev)
11:52
05.Should I go to college or not?
09:47
04.Resources to learn senior development skills
07:37
03.Passing state across components in RemixJS
06:48
02.How To Deal with Hiring Developers?
10:06
Keywords

hiring, javascript, developers

Description
I have to manage my projects and outsource them, otherwise, I would never make enough money to keep my business afloat. I have this problem, where, when I start a project, the product owner will ask questions like, "What happens if you die?" and my best answer to that is, "That's why we have employees". But, when I go to hire employees, sometimes they completely just ignore the stack that I'm using and they go off and do their own thing, which becomes difficult to manage. Should I be ruling with an iron fist, or should I just be more of a liason between my clients and my developers?
01.Why do you use the Express adapter for your app?
03:21

Looking for more content?

Have a look at these articles.

See the full blog
brown and white cat in shallow focus shot
brown and white cat in shallow focus shot
October 28th, 2021 — 5 min read
Get a catch block error message with TypeScript
by Bogomil Mihaylov
by Bogomil Mihaylov
August 27th, 2018 — 7 min read
Why and How I started public speaking