Development teams in large corporations often have workflows, processes, or custom software tailored to their specific projects. Some teams prefer a certain framework or methodology and have written custom code for their projects, while others are using a whole different methodology but developing similar functional code. Unfortunately, the reality is that teams work in silos and are reinventing the wheel somewhere down the line.
In fact, here’s what’s happening behind the scenes. Teams that aren’t using reusable, shareable components are either searching for components from open source, purchasing them from enterprise vendors, or writing their own code. But it doesn’t end there. Components available for free aren’t necessarily designed with all scenarios in mind and may lack the required features or desired
performance critical to your application. Developers end up taking the most obvious route—creating
versions of the code, enhancing it, and maintaining copies. Not only is this approach time consuming,
but it comes with huge underlying effort related to testing the components across different platforms,
browsers, operating systems, and environments. Imagine this effort being somewhat repeated across
different organizations and teams within the same corporation.