software engineering: delegate pattern : who has the responsability to create return object?
Published 1 year ago • 11 plays • Length 1:46Download video MP4
Download video MP3
Similar videos
-
1:34
software engineering: delegate pattern : delegate or delegator?
-
2:35
software engineering: delegate pattern for retrieving data v.s. using simple setters
-
2:58
software engineering: turn an asynchronous delegate pattern into a blocking method
-
4:20
software engineering: delegate vs method (5 solutions!!)
-
2:52
software engineering: delegate vs forwarding in java oop
-
1:46
software engineering: is it fine for a class that creates objects to delegate them?
-
2:14
software engineering: can classes violate single responsibility if they delegate internal tasks?
-
1:59
software engineering: is it good practice to create convenience delegate methods?
-
18:39
what are delegates? (c# basics, lambda, action, func)
-
10:22
the key management skill you need to master: delegating well
-
5:38
revealed: top 10 software development companies
-
2:27
correct use of delegate pattern
-
2:30
software engineering: how to split up a delegate class?
-
8:36
software engineering: zero behavior objects in oop - my design dilemma (10 solutions!!)
-
5:53
software engineering: looking for an effective pattern to cope with switch statements in c#
-
6:12
software engineering: what is the purpose of a delegate type variable? (6 solutions!!)
-
2:12
software engineering: how to generalize which delegate is being used from an interface?
-
7:52
software engineering: delegate vs interfaces-any more clarifications available? (9 solutions!!)
-
2:59
software engineering: design pattern for classifying a set of data
-
1:42
software engineering: the better parts and delegation: is crockford too extreme?
-
1:59
software engineering: rails: useful example of delegate and law of demeter
-
3:05
software engineering: developing an api to delegate/decouple long validation chains