4 ms·
1) You slice your project into use cases. 2) You "do" every use case end to end (including the pieces of infra needed for that use case and the user interface
by streetcat1 7y ago
1) You slice your project into use cases.
2) You "do" every use case end to end (including the pieces
of infra needed for that use case and the user interface parts).
3) You add regression tests (unit / func) for the use case.
4) Every new such use case is a new release.
This way you are always done.
- rumanator 7y agoThen there's the fact that requirements do change, and do change often, and of course there are bugs and emergent design issues.
- streetcat1 7y agoAbsolutely. But this is just another use case. The real risk of working UC by UC, is that you might get locked into bad architecture. The way to mitigate that is by using microservices.