Friday 8 February 2019, Utrecht
Robert “Uncle Bob” Martin was invited by the Rabobank to give a two-day workshop/presentation software engineers and software architects in Utrecht. I was unable to attend but watched the live-recording.
Recording on Youtube
Requirements are urgent => Architecture is important
“What is important is seldom urgent and what is urgent is seldom important.”
- Behavior is Urgent, Architecture is Important
- Stakeholders prioritize Urgency
- YOU are the engineers: responsible for Importance
Building’s architecture screams what the intent is. Why doesn’t software architecture follow this pattern?
Ivar Jacobssen’s use cases where very different from use cases now use cases coordinate the business rules (interactor) entities contain the business rules boundary objects (interfaces)
MVC is not an architecture (1970, SmallTalk) model understands business rules controller knows all about input view knows how to present the data