Artwork

Content provided by Troubleshooting Agile and A weekly problem-solving session for all things agile. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Troubleshooting Agile and A weekly problem-solving session for all things agile or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Learning Vs Design

20:51
 
Share
 

Manage episode 216643649 series 1984398
Content provided by Troubleshooting Agile and A weekly problem-solving session for all things agile. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Troubleshooting Agile and A weekly problem-solving session for all things agile or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
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.com Tweet us: twitter.com/TShootingAgile Also, 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
  continue reading

329 episodes

Artwork

Learning Vs Design

Troubleshooting Agile

95 subscribers

published

iconShare
 
Manage episode 216643649 series 1984398
Content provided by Troubleshooting Agile and A weekly problem-solving session for all things agile. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Troubleshooting Agile and A weekly problem-solving session for all things agile or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
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.com Tweet us: twitter.com/TShootingAgile Also, 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
  continue reading

329 episodes

すべてのエピソード

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide