Former Google engineer traces why Google’s monorepo tooling long lacked a standard IDE despite strict development conventions

A former Google developer tools engineer describes how Google’s main monorepo had rigorous tooling standards but left engineers free to choose their own IDEs. That freedom created fragmentation, with teams repeatedly rebuilding integrations for Bazel, Starlark, formatting, and code search until some efforts, such as IntelliJ integration, became officially staffed.

The story highlights a common tradeoff in large engineering organizations: individual editor preference can preserve developer autonomy but increase duplicated tooling work. As codebases and workflows grow more complex, companies may face growing pressure to standardize parts of the developer experience without forcing a single editor on everyone.