Artifactory can be used to prevent this 'chaos.' Block access to the most common repositories and force everyone to go through Artifactory. Then utilize an approval process to include items in Artifactory. That way not only can you document your engineering standards, but you can also enforce them.
Minimizing the number of items in your technology portfolio and the number of frameworks you're using has several benefits. You can streamline your hiring. People can more easily move from team-to-team based off their interests and business priorities. You can develop a development training plan. You've reduced your cyber-attack surface area. In my experience, if you don't apply some rigor in managing your technology portfolio then you'll end up with just about everything under the sun in your portfolio. In other words, chaos.
rbanffy•9mo ago
A good counterpoint is that evolution requires a certain amount of chaos to explore the solution space. By limiting the portfolio, you also limit how the solutions can evolve.
taylodl•9mo ago
That's managed. You don't allow everyone to run pell-mell to see what works best. They never come back together and agree on a stack, and even if they did, there's zero will or funding to retrofit the systems onto the agreed-upon stack. Meanwhile, all the political infighting by those advocating for their preferred stack creates a bad work environment and cliques.
taylodl•9mo ago
Minimizing the number of items in your technology portfolio and the number of frameworks you're using has several benefits. You can streamline your hiring. People can more easily move from team-to-team based off their interests and business priorities. You can develop a development training plan. You've reduced your cyber-attack surface area. In my experience, if you don't apply some rigor in managing your technology portfolio then you'll end up with just about everything under the sun in your portfolio. In other words, chaos.
rbanffy•9mo ago
taylodl•9mo ago
Welcome to chaos.