Illustration of a microphone

Calls with Kent C. Dodds.

You call, I'll answer.

Record your call
Listen to the podcasts here
Apple podcastsGoogle podcasts
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 — 147 episodes

147.Becoming one of the best React developer
09:47
146.Is Epic Stack beneficial for new developers?
05:03
145.How to approach imposter syndrome
05:28
144.Error Handling in Remix
06:02
143.How do you plan E2E test flows?
05:41
142.When/why should I choose SSR over CSR?
03:49
141.Side income
06:21
140.How Remix fits 6 different web apps
14:04
139.Is it really all about who knows you?
05:02
138.Tech to use for a video streaming site
02:16
137.Should we transition from Jest to Vitest
07:54
136.What's the bundle analysis story in Remix?
04:43
135.How to set titles in CatchBoundary's in Remix?
04:08
134.v2 Routing Convention
05:34
133.Seeking for solution and advice to progress
05:26
132.What is your latest thinking on render props?
05:24
131.Inline Styles vs CSS File Styles
06:43
130.Looking for the best talk idea
08:54
129.Tips on making the most of your short breaks
03:44
128.Advice for a company afraid of using Node
07:57
127.How are redux thunks implementation details?
06:28
126.What makes a good react js developer?
05:31
125.AWS Job Opportunity
03:48
124.Playwright support
03:33
123.Tips for creating a npm package (stack-supporting)
08:30
122.How close should a hook be to its usage?
03:27
121.What's your opinion on atomic design?
03:08
120.How to handle file uploads in Remix?
03:43
119.Tailwind class overriding
05:37
118.How do you deal with partial types?
04:25
117.The "remix" testing methodology
05:52
116.How to handle action matching no intent?
04:25
115.Latest practical CSS techniques (use Tailwind)
04:04
114.Middleware is an antipattern
08:01
113.How to test semantic HTML tables?
03:57
112.Appreciation
02:06
111.Testing Code in service files and NGXS Store files
03:26
110.Is using md5 as key an anti-pattern in react?
04:23
109.Why do you take short breaks when coding?
03:46
108.Is addEventListener OK again?
04:08
107.Frontend to Fullstack
04:13
106.Test Data: To BeforeAll or to BeforeEach
06:17
105.organizing course code
11:21
104.How to do feature flags with Remix?
07:09
103.Own Code vs Library
06:47
102.Would you recommend to use Playwright or Cypress?
05:52
101.How to Shamelessly Self-Promote?
05:47
100.Why are you programming in VScode?
07:22
99.Remix: ways around window undefined
05:42
98.Testing a graphical component
03:21
97.Will there be a KCD Trilogy? (Yes)
06:17
96.How do you automate KCD?
12:48
95.Question about testing a reusable component
07:01
94.Full Stack Developers... Why?
07:18
93.Mantine's callback with Remix's ActionFunction
05:21
92.How do you convince your team to use E2E?
05:03
91.Migration from React/Rails hybrid to Remix
10:32
90.Do you have any thoughts on Playwright?
04:30
89.Using cookie/privacy policies on personal websites
06:13
88.Leveling up your career while putting family first
07:02
87.Live loading data with remix
05:28
86.Using VPN during software development
03:38
85.Why is there so much hate regarding React lately?
17:24
84.Decomposing remix component
06:15
83.Jump from mid level to senior react developer
08:04
82.React app doesn't work on IE11
05:47
81.Using userEvent vs fireEvent
05:16
80.useMemo vs React.Memo when it comes to JSX
04:46
79.How to build a committed following
07:13
78.Learning Frontend Architecture
04:11
77.Querying the data in nested routes
06:40
76.Nivo charts issue
06:56
75.i18n and Remix
02:57
74. Tests for accessible error messages
03:39
73.Asserting props.onClick in react-testing-library
05:36
72.CatchBoundary on empty datasets
11:00
71.Remix Anti-patterns
04:34
70.Why Framer Motion for Animations
02:38
69.Lack of experience when problem solving
07:18
68.How to identify which button submits a form
03:30
67.Thinking process when reviewing code
06:33
66.Do you read the React source code?
04:23
65.Isolate FE and BE apps vs Remix Full Stack
03:54
64.Using Remix with a custom backend (Nestjs)
07:26
63.Feedback speed in TDD
04:55
62.Understand what's effect and what is derived state
06:27
61.Order of Courses to Take
05:24
60.State bloating vs api call (again and again)
06:40
59.Separation of rendering vs logics custom hooks
04:47
58.Imposter Syndrome and Working at FAANG
07:03
57.In a Startup only testing in the backend?
04:20
56.Using GraphQL queries in Remix loader functions
03:36
55.Servers + Databases + Remix
05:15
54.I love your website! ITS BEAUTIFUL.
01:38
53.How can I incentivize users to not share accounts?
03:19
52.Could the useState be used without the setter?
06:03
51.Bestway to reset a form
05:27
50.How to decide among advanced react patterns?
07:12
49.Handling difficult co-workers and/or leadership
05:24
48.Use React frameworks (Remix) for SPAs
05:29
47.Isolating tests
04:39
46.Versioning and dependency management for libraries
05:07
45.Full stack framework vs front-end with saas
06:34
44.Learning Gaps & Cluelessness as a Developer
07:46
43.Alfred and/or ScriptKit?
07:41
42.Why React JS?
23:22
41.Bailing out of re-rendering in useState
04:28
40.Remix Styling w/CSS in JS
08:29
39.Learning web development the right way
07:07
38.Testing a Drag and Drop Experience
03:59
37.Protected route and redirect after payment
06:17
36.Making changes on a new team
13:27
35.Building an Open Source Website
08:56
34.Question about testing alongside RTL
07:21
33.Create web components in React
07:29
32.Magic links require timely email delivery
06:48
31.Some advice for developers about the design
02:43
30.Pricing low-demand workshops
05:08
29.Why XState?
06:27
28.Forms in React
04:48
27.How small should components be
03:58
Keywords

components, granularity, small

Tweet this
Description

I was wondering how to decide when the html is too trivial to turn into a component. For example turning msg into a component. Maybe it's useful for styled components? Thanks

26.Using Fly.io Replays
12:46
25.Why is forwardRef required to limit re-renders?
07:24
24.Traditional logins vs. passwordless magic links
14:08
23.How to plan curriculum
04:48
22.Why Remix over other React frameworks?
35:44
21.What did paypal-scripts do?
06:15
20.What are your thoughts on Svelte?
11:21
19.Where did those diagrams come from?
02:39
18.Filling CS concept holes as a non-CS major?
05:48
17.How to buy for EpicReact in "installments"
06:16
16.Best approach for building headless components
09:05
15.Cypress Component Testing Library vs Jest
04:44
14.How does Remix manage many CSS files in a page?
04:16
13.Mirage JS over MSW?
06:04
12.Work Life Balance
10:02
11.How much of seniority is about code skills?
07:59
10.Firm skills
05:21
09.How to style?
09:06
08.SSG Hype
13:55
07.Managing Burnout
03:28
06.Make It Stick: Interleave Curves
05:11
05.What is the best way to go through EpicReact?
09:23
04.How do you find new technology
02:45
03.Difference in methods emanating from screen and render
04:38
02.Dealing with "act" warning on react testing
06:20
01.Reusing components between different projects
06:05

Looking for more content?

Have a look at these articles.

See the full blog
by Pathum Danthanarayana
by Pathum Danthanarayana
June 5th, 2021 — 11 min read
How to use React Context effectively
by Hudson Hintze
by Hudson Hintze
December 3rd, 2019 — 2 min read
Why your team needs TestingJavaScript.com