fuck_u_spez@lemmy.fmhy.ml to Programmer Humor@programming.dev · 2 年前Everyone should have a tool-building factory factory factoryi.ibb.coimagemessage-square59fedilinkarrow-up1586arrow-down117
arrow-up1569arrow-down1imageEveryone should have a tool-building factory factory factoryi.ibb.cofuck_u_spez@lemmy.fmhy.ml to Programmer Humor@programming.dev · 2 年前message-square59fedilink
minus-squaretatterdemalion@programming.devlinkfedilinkarrow-up2·2 年前Do you write unit tests with objects mocked via interfaces? Or polymorphism via interfaces? Those are the main reasons to use DI.
minus-squarefuck_u_spez@lemmy.fmhy.mlOPlinkfedilinkarrow-up4arrow-down3·2 年前I guess I have to start calling function invocation with generic parameters, fancy names (like “dependency injection” ^^)
minus-squareqwioeue@lemmy.worldlinkfedilinkarrow-up2·2 年前Relevant: I also prefer the simpler explanation. https://www.jamesshore.com/v2/blog/2006/dependency-injection-demystified
minus-squarematto@lemm.eelinkfedilinkarrow-up2·edit-22 年前As I read somewhere: Dependency Injection is a 25-dollar term for a 5-cent concept.
minus-squareEthan@programming.devlinkfedilinkarrow-up1·2 年前I use various strategies depending on what seems appropriate, including the two you mention. I’ve never felt the lack of DI.
Do you write unit tests with objects mocked via interfaces? Or polymorphism via interfaces? Those are the main reasons to use DI.
I guess I have to start calling function invocation with generic parameters, fancy names (like “dependency injection” ^^)
Relevant:
I also prefer the simpler explanation.
https://www.jamesshore.com/v2/blog/2006/dependency-injection-demystified
As I read somewhere:
Yea that works too.
I use various strategies depending on what seems appropriate, including the two you mention. I’ve never felt the lack of DI.