Episode 417 | Jérémie Chassaing - Caring, Context, and Iteration

Guest:

@

Jérémie Chassaing talks with Dave Rael about domain modeling, live coding, teaching programming, and communicating

Jérémie Chassaing has been practicing Domain Driven Design and Continuous Improvement for 10 years as an architect at Availpro, a channel manager for independent hotels, to increase scalability and reliability to match its rapid growth. He's an active member of the F# community. You can also see his blog thinkbeforecoding, a blog dedicated to Domain Driven Design, CQRS and Event Sourcing.

Chapters: 0:16 - Dave introduces the show and Jérémie Chassaing2:05 - How Jérémie got started in software6:59 - Jérémie on becoming a software professional and getting deep in video8:09 - Jérémie on Domain-Driven Design13:40 - "If you're not live coding you're dead coding."17:08 - Jérémie's relationship with F#19:27 - The meaning of modeling21:16 - Jérémie story of failure - ineffective communication24:19 - Long-lived teams26:15 - Jérémie's book recommendations27:40 - The things that have Jérémie most excited29:31 - Jérémie's top 3 tips for delivering more value30:33 - Keeping up with Jérémie

Resources: Eric Evans on Developer On Fire Udi Dahan on Developer On Fire Udi Dahan's Advanced Distributed Systems Design Course Command-Query Responsibility Segregation Mathias Brandewinder on Developer On Fire Sam Aaron Domain Modeling Made Functional: Tackle Software Complexity with Domain-Driven Design and F# - Scott Wlaschin Scott Wlaschin on Developer On Fire Event Storming Eric Evans: What I've learned about DDD since the book

Jérémie's book recommendation: Code: The Hidden Language of Computer Hardware and Software - Charles Petzold The Computer Boys Take Over: Computers, Programmers, and the Politics of Technical Expertise (History of Computing) - Nathan L. Ensmenger

Jérémie's top 3 tips for delivering more value: Try to care Step back and take some time to try to see a larger context around the problem Try, fail, and try again