News for hackers. Stuff that matters.
Re:Building Uber’s Go Monorepo with Bazel by gav on Thursday May 14, 2020 @12:41PM (#23181758)
It’s not risk mitigation, more a risk swap between “unknown risk”—we don’t know if this third-party product is going to meet our future needs—and “known risk”—we have full control while we are willing to write checks to fund it.

In the latter case there’s still plenty of risk: you might be spending valuable time building something that doesn’t work, is obsoleted by future change or future products; and the one that most people dismiss, you will be at the mercy of its creators. The people who build your critical technologies will have power over the organization you might regret later, and if they do leave, finding replacements can be hard and/or expensive.

Re:Building Uber’s Go Monorepo with Bazel by cle on Thursday May 14, 2020 @04:42PM (#23185137)
The net risk reduction of course depends on specific situations, it is not always better and it is not always a "swap". In some cases, eliminating unknowns reduces more risk than is added by building in-house, which is when it makes sense to build in-house.
Re:Building Uber’s Go Monorepo with Bazel by caust1c on Thursday May 14, 2020 @02:29PM (#23183418)
Spot on! Never thought about it from this perspective. :-)