1. Introduction For a long time, Dependency Injection (DI) felt unnecessary to me. I kept asking myself: “Why am I writing an extra interface when I still have to write the implementation?” Isn’t that just… overengineering? This question is surpris...
ujjwalkar.hashnode.dev3 min read
Tiffany Spark
Web designer in London. Clean code, good design, strong coffee.
the chef analogy is brilliant, honestly this is the clearest explanation of DI i have come across. the point about coding for change tomorrow not just today is the thing that finally made it click for me a while back. bookmarking this one for whenever i have to explain it to someone else.