Sounds a lot like what I hear about google. The internal tooling is second to none. "If you have a problem, 5 people already solved it in a really elegant easy to use way already"
I wish I was working in such an ecosystem. :(
I wish I was working in such an ecosystem. :(
Bazel, Google's build tool is a good example of this. Google actually open-sourced most of Bazel a few years ago, but as far as I know, it hasn't gotten much uptake. It requires doing a bunch of boring configuration work to use it. But as someone who used it internally I definitely prefer it to all the alternatives, due to its speed and reliability.
Although Bazel is still in beta, more and more companies are using it (e.g. Dropbox, Huawei, SpaceX, Pinterest, Stripe - see https://github.com/bazelbuild/bazel/wiki/Bazel-Users) or interested enough to attend the recent Bazel conference (see https://conf.bazel.build/about).
I can imagine there is some fear of espionage or sabotage but I'm just asking the boring stuff about deploying a (web) front end system.
My impression is that for local stuff their tooling is not much better than public. They have a lot more reliance on logging.
I’ve never worked there so this is just all second hand info.