software engineering: clean architecture: use case containing the presenter or returning data?
Published 2 years ago • 12 plays • Length 8:50Download video MP4
Download video MP3
Similar videos
-
2:30
software engineering: clean architecture use case testing
-
4:05
software engineering: what should presenters return in clean architecture? (3 solutions!!)
-
3:23
clean architecture - what is the difference between use cases and core services?
-
4:12
clean architecture, good approaches to avoid hard-coding the creation of entities on the use case
-
2:46
software engineering: use case interactions in clean architecture
-
1:44
software engineering: understanding clean architecture
-
3:01
software engineering: changing repository during use cases/interactors in clean architecture
-
3:01
software engineering: clean architecture - controllers and presenters
-
1:47
clean architecture: should users go in the use case layer or the domain layer?
-
2:27
software engineering: clean architecture - how do i deal with use case reuse?
-
3:25
software engineering: clean architecture - too many use case classes (4 solutions!!)
-
2:40
software engineering: clean architecture: can use cases imply ui?
-
1:36
software engineering: listen for data(base) changes using clean architecture
-
2:59
software engineering: clean architecture: should each view have its own presenter and viewmodel?
-
3:02
software engineering: what naming convention should i use in clean architecture? (2 solutions!!)
-
3:23
how to split up use cases in clean architecture? (dealing with use case dependencies)?
-
3:08
clean architecture - how to pass request data towards inner, domain level use cases?
-
3:48
software engineering: clean architecture: what is the view model? (2 solutions!!)