BROADCASTS.com

Published: June 25, 2020, 7:13 a.m.

Christian Vogel, Software and Product Engineer at DAN.com, says that creating their own React pattern at DAN has helped them streamline their software development. In short, it removes the need to make state management a priority, which not only makes Christian’s coding faster, but also — he says — more fun. In this podcast conversation, he shares what the DAN React pattern looks like on a component level, how it’s set up, the practical impacts it’s had on his team’s workflow, and some things to consider when setting up your own React pattern.

Follow our conversation by using the chapter breakdown below, or check out the full transcript of the episode on the blog here! (https://bit.ly/2BHhRIo) 

Also, we encourage you to reach out to Christian after listening! Make notes during the episode of any questions or comments you think of, and message him via LinkedIn or Twitter — he’ll gladly answer any questions you have!

Podcast chapters:[03:42] Intro to Christian’s role at DAN.com, and what they do as a company
[06:32] What is the DAN React pattern?
[09:07] Benefits of the DAN React pattern for DAN.com’s software development
[12:56] How the DAN React pattern works: Components and setup
[16:57] Use cases for when (and when not) Redux might be the better pattern
[18:36] Why the simplicity of the DAN React pattern is so useful
[20:21] How this pattern helped build a live, internal ‘alert system’ within two weeks
[23:19] The potential for this kind of React pattern
[24:22] Christian’s advice for anyone wanting to build their own React pattern
[27:12] Final summary, takeaway points, and closing thoughts