Overhears colleague say 'Ohh there's a plugin for that'. Few weeks later i find the dumb fuck added it to the codebase and not use the dependency manager. I'd happily shoot the senior Dev who peer reviewed it but looks like this pleb merged straight in!

With a codebase overflowing with duplicate frameworks and unused jquery plugins I'll be burning the god damn place down come next week!

What's wrong with that? I wouldn't trust some plugin repo. What if they decide to delete that plugin tomorrow? If it's in your own repo it's always there.

@Double-A if you're going to use a plugin that's likely to get deleted over night then you should really fork it and point your dependency manager to that URL. The chances of that are quite slim if you're working on large systems that must be stable 100% of the time. I've been brought up in an industry that plugins are the very last resort if a custom built functionality wouldn't be cost effective. If a plugin is used it must meet a very high criteria.