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.

If recording isn't an option, you can also type your question and we'll generate the audio for you.

I look forward to hearing from you!

Record your call

Calls with Kent C. Dodds Season 1 — 75 episodes

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
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.Taste, simplicity, and AI-era product judgment with Michael Shimeles
40:34
17.How to buy for EpicReact in "installments"
06:16
16.Know your customer better than your code - product engineering with Lucas Wargha
47:36
16.Best approach for building headless components
09:05
15.Demos, feedback loops, and AI-era product judgment with Ruben Casas
43:19
15.Cypress Component Testing Library vs Jest
04:44
14.The technical person in the room - product engineering with Sean Roberts
44:15
14.How does Remix manage many CSS files in a page?
04:16
13.Software architecture, human judgment, and AI's limits with Grady Booch
47:00
13.Mirage JS over MSW?
06:04
12.User outcomes, workflow design, and biotech software - product engineering with Swizec Teller
40:14
12.Work Life Balance
10:02
11.User empathy, feedback loops, and what not to build - product engineering with Jack Ryan
53:23
11.How much of seniority is about code skills?
07:59
10.Primitives, agent UX, and Executor - product engineering with Rhys Sullivan
41:24
10.Firm skills
05:21
09.Customer research, desire, and Sales Safari - product engineering with Alex Hillman
71:47
09.How to style?
09:06
08.What the devil is a Factory Engineer?!
30:45
Keywords

Better, with, Kent

StarPost this
Description
Kent reacts to Zach Lloyd's Warp memo on "factory engineers" — where the software-factory vision is right, where it misses product context, and why factory work still comes back to users.

{{chapters}}

Better with Kent — durable skills for people who ship software.

Warp CEO Zach Lloyd told his team they are now factory engineers, not product engineers. Kent reads the memo aloud and pressure-tests the framing: automated development, cloud software factories, agent workflows, and the metrics that can game you if you forget what users are paying for.

He agrees with a lot of the direction — build the system agents work in, measure throughput, tighten the loop — but pushes back on anything that treats the product as optional. Internal tools still have users. Factory efficiency only matters when the right work goes in. And yes, the memo's last word is still product.

If you're trying to make sense of agentic engineering without losing product judgment, this is the durable-skills read-through.

Links

08.Speed, prioritization, and maintainability — product engineering with Julius Marminge
42:09
08.SSG Hype
13:55
07.I got attacked! - How I used my AI agent to fight back!
11:54
07.Stakeholder empathy, UX, and durable product skills — product engineering with Jamon Holmgren
56:25
07.Managing Burnout
03:28
06.I built my own OpenClaw
22:10
06.Watch users, fix systems, and design for humanity — product engineering with Don Norman
76:29
06.Make It Stick: Interleave Curves
05:11
05.Pragmatic Loop Engineering for AI Coding Agents
14:00
05.Human factors, product debt, and industrial design — product engineering with Will King
61:56
05.What is the best way to go through EpicReact?
09:23
04.Stop Taking Tickets, Start Applying Jobs Theory
21:02
04.Vertical slices, Solo, and empathy — product engineering with Aaron D. Francis
45:40
04.How do you find new technology
02:45
03.How an AI Agent Deleted PocketOS Production in 9 Seconds
16:18
03.Foundations, feedback, and agents — Dillon Mulroy on product at Cloudflare
49:03
03.Difference in methods emanating from screen and render
04:38
02.How to Prioritize Software Tasks
16:11
02.The right thing before the thing right — product engineering with Wayne Allan
50:32
02.Dealing with "act" warning on react testing
06:20
01.What Software Engineers Need in 2026
29:32
01.Product sense, restraint, and OpenCode with Dax Raad
54:00
01.Reusing components between different projects
06:05
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
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.Taste, simplicity, and AI-era product judgment with Michael Shimeles
40:34
17.How to buy for EpicReact in "installments"
06:16
16.Know your customer better than your code - product engineering with Lucas Wargha
47:36
16.Best approach for building headless components
09:05
15.Demos, feedback loops, and AI-era product judgment with Ruben Casas
43:19
15.Cypress Component Testing Library vs Jest
04:44
14.The technical person in the room - product engineering with Sean Roberts
44:15
14.How does Remix manage many CSS files in a page?
04:16
13.Software architecture, human judgment, and AI's limits with Grady Booch
47:00
13.Mirage JS over MSW?
06:04
12.User outcomes, workflow design, and biotech software - product engineering with Swizec Teller
40:14
12.Work Life Balance
10:02
11.User empathy, feedback loops, and what not to build - product engineering with Jack Ryan
53:23
11.How much of seniority is about code skills?
07:59
10.Primitives, agent UX, and Executor - product engineering with Rhys Sullivan
41:24
10.Firm skills
05:21
09.Customer research, desire, and Sales Safari - product engineering with Alex Hillman
71:47
09.How to style?
09:06
08.What the devil is a Factory Engineer?!
30:45
Keywords

Better, with, Kent

StarPost this
Description
Kent reacts to Zach Lloyd's Warp memo on "factory engineers" — where the software-factory vision is right, where it misses product context, and why factory work still comes back to users.

{{chapters}}

Better with Kent — durable skills for people who ship software.

Warp CEO Zach Lloyd told his team they are now factory engineers, not product engineers. Kent reads the memo aloud and pressure-tests the framing: automated development, cloud software factories, agent workflows, and the metrics that can game you if you forget what users are paying for.

He agrees with a lot of the direction — build the system agents work in, measure throughput, tighten the loop — but pushes back on anything that treats the product as optional. Internal tools still have users. Factory efficiency only matters when the right work goes in. And yes, the memo's last word is still product.

If you're trying to make sense of agentic engineering without losing product judgment, this is the durable-skills read-through.

Links

08.Speed, prioritization, and maintainability — product engineering with Julius Marminge
42:09
08.SSG Hype
13:55
07.I got attacked! - How I used my AI agent to fight back!
11:54
07.Stakeholder empathy, UX, and durable product skills — product engineering with Jamon Holmgren
56:25
07.Managing Burnout
03:28
06.I built my own OpenClaw
22:10
06.Watch users, fix systems, and design for humanity — product engineering with Don Norman
76:29
06.Make It Stick: Interleave Curves
05:11
05.Pragmatic Loop Engineering for AI Coding Agents
14:00
05.Human factors, product debt, and industrial design — product engineering with Will King
61:56
05.What is the best way to go through EpicReact?
09:23
04.Stop Taking Tickets, Start Applying Jobs Theory
21:02
04.Vertical slices, Solo, and empathy — product engineering with Aaron D. Francis
45:40
04.How do you find new technology
02:45
03.How an AI Agent Deleted PocketOS Production in 9 Seconds
16:18
03.Foundations, feedback, and agents — Dillon Mulroy on product at Cloudflare
49:03
03.Difference in methods emanating from screen and render
04:38
02.How to Prioritize Software Tasks
16:11
02.The right thing before the thing right — product engineering with Wayne Allan
50:32
02.Dealing with "act" warning on react testing
06:20
01.What Software Engineers Need in 2026
29:32
01.Product sense, restraint, and OpenCode with Dax Raad
54:00
01.Reusing components between different projects
06:05
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
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.Taste, simplicity, and AI-era product judgment with Michael Shimeles
40:34
17.How to buy for EpicReact in "installments"
06:16
16.Know your customer better than your code - product engineering with Lucas Wargha
47:36
16.Best approach for building headless components
09:05
15.Demos, feedback loops, and AI-era product judgment with Ruben Casas
43:19
15.Cypress Component Testing Library vs Jest
04:44
14.The technical person in the room - product engineering with Sean Roberts
44:15
14.How does Remix manage many CSS files in a page?
04:16
13.Software architecture, human judgment, and AI's limits with Grady Booch
47:00
13.Mirage JS over MSW?
06:04
12.User outcomes, workflow design, and biotech software - product engineering with Swizec Teller
40:14
12.Work Life Balance
10:02
11.User empathy, feedback loops, and what not to build - product engineering with Jack Ryan
53:23
11.How much of seniority is about code skills?
07:59
10.Primitives, agent UX, and Executor - product engineering with Rhys Sullivan
41:24
10.Firm skills
05:21
09.Customer research, desire, and Sales Safari - product engineering with Alex Hillman
71:47
09.How to style?
09:06
08.What the devil is a Factory Engineer?!
30:45
Keywords

Better, with, Kent

StarPost this
Description
Kent reacts to Zach Lloyd's Warp memo on "factory engineers" — where the software-factory vision is right, where it misses product context, and why factory work still comes back to users.

{{chapters}}

Better with Kent — durable skills for people who ship software.

Warp CEO Zach Lloyd told his team they are now factory engineers, not product engineers. Kent reads the memo aloud and pressure-tests the framing: automated development, cloud software factories, agent workflows, and the metrics that can game you if you forget what users are paying for.

He agrees with a lot of the direction — build the system agents work in, measure throughput, tighten the loop — but pushes back on anything that treats the product as optional. Internal tools still have users. Factory efficiency only matters when the right work goes in. And yes, the memo's last word is still product.

If you're trying to make sense of agentic engineering without losing product judgment, this is the durable-skills read-through.

Links

08.Speed, prioritization, and maintainability — product engineering with Julius Marminge
42:09
08.SSG Hype
13:55
07.I got attacked! - How I used my AI agent to fight back!
11:54
07.Stakeholder empathy, UX, and durable product skills — product engineering with Jamon Holmgren
56:25
07.Managing Burnout
03:28
06.I built my own OpenClaw
22:10
06.Watch users, fix systems, and design for humanity — product engineering with Don Norman
76:29
06.Make It Stick: Interleave Curves
05:11
05.Pragmatic Loop Engineering for AI Coding Agents
14:00
05.Human factors, product debt, and industrial design — product engineering with Will King
61:56
05.What is the best way to go through EpicReact?
09:23
04.Stop Taking Tickets, Start Applying Jobs Theory
21:02
04.Vertical slices, Solo, and empathy — product engineering with Aaron D. Francis
45:40
04.How do you find new technology
02:45
03.How an AI Agent Deleted PocketOS Production in 9 Seconds
16:18
03.Foundations, feedback, and agents — Dillon Mulroy on product at Cloudflare
49:03
03.Difference in methods emanating from screen and render
04:38
02.How to Prioritize Software Tasks
16:11
02.The right thing before the thing right — product engineering with Wayne Allan
50:32
02.Dealing with "act" warning on react testing
06:20
01.What Software Engineers Need in 2026
29:32
01.Product sense, restraint, and OpenCode with Dax Raad
54:00
01.Reusing components between different projects
06:05
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
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.Taste, simplicity, and AI-era product judgment with Michael Shimeles
40:34
17.How to buy for EpicReact in "installments"
06:16
16.Know your customer better than your code - product engineering with Lucas Wargha
47:36
16.Best approach for building headless components
09:05
15.Demos, feedback loops, and AI-era product judgment with Ruben Casas
43:19
15.Cypress Component Testing Library vs Jest
04:44
14.The technical person in the room - product engineering with Sean Roberts
44:15
14.How does Remix manage many CSS files in a page?
04:16
13.Software architecture, human judgment, and AI's limits with Grady Booch
47:00
13.Mirage JS over MSW?
06:04
12.User outcomes, workflow design, and biotech software - product engineering with Swizec Teller
40:14
12.Work Life Balance
10:02
11.User empathy, feedback loops, and what not to build - product engineering with Jack Ryan
53:23
11.How much of seniority is about code skills?
07:59
10.Primitives, agent UX, and Executor - product engineering with Rhys Sullivan
41:24
10.Firm skills
05:21
09.Customer research, desire, and Sales Safari - product engineering with Alex Hillman
71:47
09.How to style?
09:06
08.What the devil is a Factory Engineer?!
30:45
Keywords

Better, with, Kent

StarPost this
Description
Kent reacts to Zach Lloyd's Warp memo on "factory engineers" — where the software-factory vision is right, where it misses product context, and why factory work still comes back to users.

{{chapters}}

Better with Kent — durable skills for people who ship software.

Warp CEO Zach Lloyd told his team they are now factory engineers, not product engineers. Kent reads the memo aloud and pressure-tests the framing: automated development, cloud software factories, agent workflows, and the metrics that can game you if you forget what users are paying for.

He agrees with a lot of the direction — build the system agents work in, measure throughput, tighten the loop — but pushes back on anything that treats the product as optional. Internal tools still have users. Factory efficiency only matters when the right work goes in. And yes, the memo's last word is still product.

If you're trying to make sense of agentic engineering without losing product judgment, this is the durable-skills read-through.

Links

08.Speed, prioritization, and maintainability — product engineering with Julius Marminge
42:09
08.SSG Hype
13:55
07.I got attacked! - How I used my AI agent to fight back!
11:54
07.Stakeholder empathy, UX, and durable product skills — product engineering with Jamon Holmgren
56:25
07.Managing Burnout
03:28
06.I built my own OpenClaw
22:10
06.Watch users, fix systems, and design for humanity — product engineering with Don Norman
76:29
06.Make It Stick: Interleave Curves
05:11
05.Pragmatic Loop Engineering for AI Coding Agents
14:00
05.Human factors, product debt, and industrial design — product engineering with Will King
61:56
05.What is the best way to go through EpicReact?
09:23
04.Stop Taking Tickets, Start Applying Jobs Theory
21:02
04.Vertical slices, Solo, and empathy — product engineering with Aaron D. Francis
45:40
04.How do you find new technology
02:45
03.How an AI Agent Deleted PocketOS Production in 9 Seconds
16:18
03.Foundations, feedback, and agents — Dillon Mulroy on product at Cloudflare
49:03
03.Difference in methods emanating from screen and render
04:38
02.How to Prioritize Software Tasks
16:11
02.The right thing before the thing right — product engineering with Wayne Allan
50:32
02.Dealing with "act" warning on react testing
06:20
01.What Software Engineers Need in 2026
29:32
01.Product sense, restraint, and OpenCode with Dax Raad
54:00
01.Reusing components between different projects
06:05
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
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.Taste, simplicity, and AI-era product judgment with Michael Shimeles
40:34
17.How to buy for EpicReact in "installments"
06:16
16.Know your customer better than your code - product engineering with Lucas Wargha
47:36
16.Best approach for building headless components
09:05
15.Demos, feedback loops, and AI-era product judgment with Ruben Casas
43:19
15.Cypress Component Testing Library vs Jest
04:44
14.The technical person in the room - product engineering with Sean Roberts
44:15
14.How does Remix manage many CSS files in a page?
04:16
13.Software architecture, human judgment, and AI's limits with Grady Booch
47:00
13.Mirage JS over MSW?
06:04
12.User outcomes, workflow design, and biotech software - product engineering with Swizec Teller
40:14
12.Work Life Balance
10:02
11.User empathy, feedback loops, and what not to build - product engineering with Jack Ryan
53:23
11.How much of seniority is about code skills?
07:59
10.Primitives, agent UX, and Executor - product engineering with Rhys Sullivan
41:24
10.Firm skills
05:21
09.Customer research, desire, and Sales Safari - product engineering with Alex Hillman
71:47
09.How to style?
09:06
08.What the devil is a Factory Engineer?!
30:45
Keywords

Better, with, Kent

StarPost this
Description
Kent reacts to Zach Lloyd's Warp memo on "factory engineers" — where the software-factory vision is right, where it misses product context, and why factory work still comes back to users.

{{chapters}}

Better with Kent — durable skills for people who ship software.

Warp CEO Zach Lloyd told his team they are now factory engineers, not product engineers. Kent reads the memo aloud and pressure-tests the framing: automated development, cloud software factories, agent workflows, and the metrics that can game you if you forget what users are paying for.

He agrees with a lot of the direction — build the system agents work in, measure throughput, tighten the loop — but pushes back on anything that treats the product as optional. Internal tools still have users. Factory efficiency only matters when the right work goes in. And yes, the memo's last word is still product.

If you're trying to make sense of agentic engineering without losing product judgment, this is the durable-skills read-through.

Links

08.Speed, prioritization, and maintainability — product engineering with Julius Marminge
42:09
08.SSG Hype
13:55
07.I got attacked! - How I used my AI agent to fight back!
11:54
07.Stakeholder empathy, UX, and durable product skills — product engineering with Jamon Holmgren
56:25
07.Managing Burnout
03:28
06.I built my own OpenClaw
22:10
06.Watch users, fix systems, and design for humanity — product engineering with Don Norman
76:29
06.Make It Stick: Interleave Curves
05:11
05.Pragmatic Loop Engineering for AI Coding Agents
14:00
05.Human factors, product debt, and industrial design — product engineering with Will King
61:56
05.What is the best way to go through EpicReact?
09:23
04.Stop Taking Tickets, Start Applying Jobs Theory
21:02
04.Vertical slices, Solo, and empathy — product engineering with Aaron D. Francis
45:40
04.How do you find new technology
02:45
03.How an AI Agent Deleted PocketOS Production in 9 Seconds
16:18
03.Foundations, feedback, and agents — Dillon Mulroy on product at Cloudflare
49:03
03.Difference in methods emanating from screen and render
04:38
02.How to Prioritize Software Tasks
16:11
02.The right thing before the thing right — product engineering with Wayne Allan
50:32
02.Dealing with "act" warning on react testing
06:20
01.What Software Engineers Need in 2026
29:32
01.Product sense, restraint, and OpenCode with Dax Raad
54:00
01.Reusing components between different projects
06:05

Looking for more content?

Have a look at these articles.

See the full blog
git diff contains the knowledge we_seek
October 27th, 2015 — 5 min read
Please, don't commit commented out code
Photo by [Pathum Danthanarayana](https://unsplash.com/photos/KLbUohEjb04)
June 5th, 2021 — 11 min read
How to use React Context effectively