I previously discussed how the main codebase at Google enforces strict tooling and conventions to allow the codebase to scale. For many years, there was one glaring exception: the IDE.
Context: I worked at Google from 2011 to 2024. Some of the information might be approximative, I’ll update it if...January 2023 was a chaotic month inside Google. Without warning, the company announced 12,000 layoffs—roughly 6% of its global workforce. Panic set in as employees woke up to find their access suddenly revoked. There were stories of people discovering their fate while on parental leave, others mid-p...
Continue reading...I’ve spent over a decade working on developer infrastructure at Google, contributing to areas like the build system, IDE, refactoring tools, and linters. Contributing to the evolution of one of the world’s largest codebases was a challenging task. What might seem like a tiny change can ripple across...
Continue reading...Back in September 2012, I was a junior engineer at Google, working on Bazel (Google’s build tool, also known internally as Blaze). One day, a mysterious calendar invite landed in my inbox. It was sent by two engineers in the US, and I was invited along with my team lead.
I...
Continue reading...