A listener asks us how we reconcile the perceived conflict between learning and design - if you're iterating fast, how can you also build solid, scalable architecture? With examples from OO and Domain-Driven Design, we describe how early agile adopters addressed this issue (and how the meaning of "design" has evolved), and then make suggestions for modern teams.SHOW LINKS:- Elephant Carpaccio: https://dzone.com/articles/elephant-carpaccio-user- OO design: https://en.wikipedia.org/wiki/Object-oriented_design- DDD: https://en.wikipedia.org/wiki/Domain-driven_design***We'd love to hear any thoughts, ideas, or feedback you have about the show.Email us: see link on troubleshootingagile.comTweet us: twitter.com/TShootingAgileAlso, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2