ios dev: avoid leaking dependencies into your view | ed clips
Published 2 years ago • 653 plays • Length 2:42Download video MP4
Download video MP3
Similar videos
-
1:19
ios dev: decouple presentation layer and views using dependency inversion | ed clips
-
2:42
ios dev: how to inject dependencies to the first viewcontroller created from storyboard? | ed clips
-
5:37
ios dev: this is why module separation is a case-by-case decision | ed clips
-
3:31
ios dev: simplify and make your code more reusable with dependency injection | ed clips
-
14:05
ios dev: this mindset will help you decouple the tests and the implementation details. | ed clips
-
3:16
ios dev: avoid putting logic to the spy or stub! | ed clips
-
15:27
ios dev: use this technique to decouple your module from infrastructure details | ed clips
-
10:12
ios dev: what's the problem with persisting a model that has a closure? | ed clips
-
29:29
mvvm dependency injection in swift | unit testing | ios
-
14:23
swift closures explained
-
5:48
why node.js is the wrong choice for apis (and what to use instead)
-
2:46
ios dev: understanding this in the ui can help you manage dependencies in large-scale apps
-
1:07
ios dev: do this to reuse logic across apps easily | ed clips
-
2:57
ios dev: how to separate navigation responsibility from view controller? | ed clips
-
2:05
ios dev: how to solve protocol constraints with generics? | ed clips
-
10:16
ios dev: how to decouple the viewmodels with interface segregation principle? | ed clips
-
8:19
ios dev: how to decouple the ui layer and the domain layer? | ed clips
-
1:56
ios dev: viewmodels don't need to talk to apis or coredata directly | ed clips
-
2:58
ios dev: is it better to use delegates or closures for async operations? | ed clips
-
2:45
ios dev: this is how to eliminate boilerplate with mvvm | ed clips
-
2:40
ios dev: this is why you should test your code through public interfaces | ed clips
-
1:05
ios devs need to understand the full stack? | ed clips