Goodreads helps you follow your favorite authors. Be the first to learn about new releases!
Start by following Scott Millett.
Showing 1-8 of 8
“As your product evolves, adding new features becomes as easy as it was in the good old days of greenfield development.”
― Patterns, Principles, and Practices of Domain-Driven Design
― Patterns, Principles, and Practices of Domain-Driven Design
“A lack of focus on a shared language and knowledge of the problem domain results in a codebase that works but does not reveal the intent of the business.”
― Patterns, Principles, and Practices of Domain-Driven Design
― Patterns, Principles, and Practices of Domain-Driven Design
“Any team can write a software product to meet the needs of a set of use cases,
but teams that put time and effort into the problem domain they are working on can consistently evolve the product to meet new business use cases.”
― Patterns Principles and Practices of Domain Driven Design
but teams that put time and effort into the problem domain they are working on can consistently evolve the product to meet new business use cases.”
― Patterns Principles and Practices of Domain Driven Design
“Any
team can write a software product to meet the needs of a set of use cases, but teams that put time
and effort into the problem domain they are working on can consistently evolve the product to meet
new business use cases.”
― Patterns Principles and Practices of Domain Driven Design
team can write a software product to meet the needs of a set of use cases, but teams that put time
and effort into the problem domain they are working on can consistently evolve the product to meet
new business use cases.”
― Patterns Principles and Practices of Domain Driven Design
“Any team can write a software product to meet the needs of a set of use cases, but teams that put time
and effort into the problem domain they are working on can consistently evolve the product to meet new business use cases.”
― Patterns Principles and Practices of Domain Driven Design
and effort into the problem domain they are working on can consistently evolve the product to meet new business use cases.”
― Patterns Principles and Practices of Domain Driven Design
“Areas of low complexity or that are unlikely to be invested in can be built without the need for perfect code quality; working software is good enough. Sometimes feedback and first-to-market are core to the success of a product; in this instance, it can make business sense to get working software up as soon as possible, whatever the architecture.”
― Patterns, Principles, and Practices of Domain-Driven Design
― Patterns, Principles, and Practices of Domain-Driven Design
“The DDD philosophy is not about following a set of rules or applying coding patterns. It is a process of learning. The journey is far more important than the destination, and the journey is all about exploring your problem domain in collaboration with domain experts rather than how many design patterns you can employ in your solution.”
― Patterns Principles and Practices of Domain Driven Design
― Patterns Principles and Practices of Domain Driven Design
“Domain-Driven Design (DDD) is a process that aligns your code with the reality of your problem domain.”
― Patterns Principles and Practices of Domain Driven Design
― Patterns Principles and Practices of Domain Driven Design
