On: Why I Don't Teach SOLID

[ChicagoDave]

There are ways to talk about it that help developers understand. Instead of focusing on the pattern overall, talk about the core dependency manager as often as possible. If a junior or mid-level developer gets it pounded into their heads that there's a magical piece of code doing some stuff they can't see, then they might just figure things out.

But that's only a band-aid. It's my experience that they still won't truly understand why they can't just call A from B and they certainly don't understand how to get B in A through an injection.

[tel → ChicagoDave]

It always just feels like unnecessary terminology and technology. Here's the core pattern.

    function app(injected) {
      return injected.doSomething();
    }

    function main() {

      var injectable = new Injectable();
      var result     = app(injectable);
      console.log(result);

    }

Everything else is around obscuring that core pattern or making it "convenient" by providing some kind of naming abstraction. That at least makes a little bit of sense in Javascript, like above, since you need the stringy names to simulate types... but in any language with nominal typing you're just killing yourself with unnecessary complexity.