Use Others Software #

There is a positive stigma associated with writing software for the sake of writing software just because someone is capable of writing it. Every builder can build a hammer, that doesn’t me any of them actually builds their own hammer unless the project depends on that custom build. Writing software systems from scratch for a project work only for proof of concepts or solving highly defined problems in which you required to squeeze out every bit of performance. By doing this

When that is not the case, you are always better of by using software others wrote for common problems to solve your business cases because the only way to make any system more reliable is to push to the limits and there is no better example of this than the open source software out there. Used by many, in many ways that it wasn’t intended for, at scales for which it was not designed for.

To be clear, this has nothing to do with the headcount of your team. If you look at how large software companies operate they have internal teams building libraries and frameworks, sometimes they even open source them, to be used in their project. The only two concerns you should be aware of is how much of the of application performance is impacted by the extra layers of software and how much the developer productivity is impacted by the extra bloat. 

When those two concerns are taken into account and the frameworks and library are built with those two at the top of their priorities there is no good reason not to use them.