13:15 "Injectables -- Classes that you should be asking for". Translations (I think): "you" = "the code of some class that you are writing"; "Class" = "object fulfilling an interface spec"; "asking for" = "the class you are writing requires user code to supply said object via the constructor, property or method parameter". In other words: When writing a class, design it to require that a user of that class supply all needed objects via constructor, properties or method parameters (according to criteria in preceding slides).
ninjas, petals, beer, translation .. all very nice. Abstraction is great. But I never see an example with customers, database access, invoices, stocks, webhooks, etc ... A real-world example of the need for injection looks complicated, but is in fact way more easy to comprehend then a ninja with a sword, a translation with a dictionary ... etc ...
Very interesting pattern, but what about performance of such pattern? In my opinion, any action in such application will be bloated with hugely overheaded calls. Maybe this approach is good for small/mid sized projects with 50-200k lines of code. How readable will be a 2m (million) code base written in such way? There is no way 1 single interface unit would exist or it would be enormously huge. Split? This will lead to tens and hundred of interface units.
10:30 "Property Injection... Normally should provide a default implementation -- Can be functionless so that there are no nil values" What does "functionless" mean in this context?
13:15 "Injectables -- Classes that you should be asking for". Translations (I think): "you" = "the code of some class that you are writing"; "Class" = "object fulfilling an interface spec"; "asking for" = "the class you are writing requires user code to supply said object via the constructor, property or method parameter". In other words: When writing a class, design it to require that a user of that class supply all needed objects via constructor, properties or method parameters (according to criteria in preceding slides).
ninjas, petals, beer, translation .. all very nice. Abstraction is great. But I never see an example with customers, database access, invoices, stocks, webhooks, etc ... A real-world example of the need for injection looks complicated, but is in fact way more easy to comprehend then a ninja with a sword, a translation with a dictionary ... etc ...
There is an error when parameters are moved to dpr-filen. They are not used in doorderprocessing
the Link to the code is no longer valid
Very interesting pattern, but what about performance of such pattern? In my opinion, any action in such application will be bloated with hugely overheaded calls. Maybe this approach is good for small/mid sized projects with 50-200k lines of code. How readable will be a 2m (million) code base written in such way? There is no way 1 single interface unit would exist or it would be enormously huge. Split? This will lead to tens and hundred of interface units.
11:10 Presumably in this code the FNinjaStar field is superfluous?
10:30 "Property Injection... Normally should provide a default implementation -- Can be functionless so that there are no nil values" What does "functionless" mean in this context?
A little buggy explanation