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:
- - Dave introduces the show and Jérémie Chassaing
- - How Jérémie got started in software
- - Jérémie on becoming a software professional and getting deep in video
- - Jérémie on Domain-Driven Design
- - "If you're not live coding you're dead coding."
- - Jérémie's relationship with F#
- - The meaning of modeling
- - Jérémie story of failure - ineffective communication
- - Long-lived teams
- - Jérémie's book recommendations
- - The things that have Jérémie most excited
- - Jérémie's top 3 tips for delivering more value
- - 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:
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