Tag Archives: DDD

Episode 187: Domain Driven Yak Symmathesy with Jessica Kerr

by

1

 

Tony and Craig are at YOW! Conference in Brisbane and chat to Jessica Kerr, software developer, consultant and symmathecist (look it up or listen to the podcast) and apart from our first live podcast sneeze they talk about:

 
  • YOW! 2018 keynote “The Origins of Opera and the Future of Programming“
  • YOW! 2018 talk “Shaving the Golden Yak“
  • Great teams make great people – if you want to become great as a developer, focus on the team
  • You can’t document what is obvious to you – whenever you say the word obviously, replace it with “I cant explain it, but…”
  • Yak shaving – all the tasks that you do that get in the way of your work
  • If you are an agile person but you wish agile had more code in it – go to the Domain Driven Design community
  • We need to embrace complexity in the business domain – the code should be a tool to learn about the business domain
  • Code doesn’t wait for design, it participates in design
  • Atomist – automation for DevOps

TheAgileRevolution-187 (30 minutes)

Advertisement

Episode 127 – Storming DD’s with Paul Rayner

by

2

Craig chats with Paul Rayner, a BDD and DDD expert who helps people bridge the gap of collaborative design between developers and business representatives, at YOW! West in Perth, and two old friends talk about the following:

* Agile Alliance Functional Testing Tool workshop (2011 in Salt Lake City)
* “Domain Driven Design” (Eric Evans) and “Working Effectively with Legacy Code” (Michael Feathers)
* The heart of DDD is about developing a rich model to allow you to deal with complex business domains
* Domain Driven Design Europe conference
* Design done well should pay off immediately, as well as in the medium to long term as well
* There are lot of overlaps between DDD and BDD, particularly the use of an ubiquitous language, BDD is a test first way to drive out your domain model
* YOW! West Keynote “EventStorming”
* Given When Then has a close relationship to modelling your domain events – a good model is one you can make assertions against
* “User Story Mapping” (Jeff Patton) is an example of how the community has started to build useful collaborative tools
* Example Mapping (Matt Wynne) visualises the perspectives of the Three Amigos and puts the focus on our understandings and our ignorances and provides a technique for the conversation
* Deliberate Discovery (Dan North and Liz Keogh) – where is our ignorance
* “Introducing EventStorming” (Alberto Brandolini) is a way of mapping out the domain or the business process using coloured sticky notes – what are the important events to support the behaviour required in our system
* You get a lot better result when you start at the end and work backwards to find insights
* Can use EventStorming to support lean processes such as value stream mapping (Craig’s lightbulb moment)
* “Coaching Agile Teams” (Lyssa Adkins) and how to make yourself a better coach
* Resistance as a Resource (Dale Emery) – helps to have a champion that you can support
* DDD continues to grow and evolve – the popularity of EventSourcing and CQRS have helped this

TheAgile Revolution-127 (48 minutes)