Retrospective
Say What, Why, and for Whom Before How in order to describe goals and constraints, not implementation details. Say what to build but don’t say how to build it; let developers discover the how and abstract the how with the what. This helps hide implementation details so code is simpler to work with and less costly to extend. When stories replace requirements and development becomes discovery, we build a better product than if we’d tried to figure it out up front.
In this chapter, we discovered…
-
By focusing on what the software should do instead of how it should be done, developers are free to discover the best implementations.
-
To build better-quality software, you need to know how to communicate with the people around you.
-
Shifting ...
Get Beyond Legacy Code now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
