GoKawiilTwo months ago I was fired by Google for creating the Google Workspace CLI. It went viral, hit #1 on Hacker News, gained thousands of GitHub stars and many thousands of actual users in just a couple days. It was an incredible, confusing journey, from directors and leaders asking what they could learn from the tool to getting grilled by legal about why the Google logo and brand colors are on the Google Workspace GitHub code repositories. I think the cause was that Workspace and certain leaders (and projects) were afraid of being disrupted. But the fear wasn't specific to my CLI, it was a broader fear in what agents meant for Workspace. Either way, the irony of my termination was the announcement at Google Cloud Next two days before I was fired that an official Workspace CLI was coming. I want this out there because it is easier for me to explain my story and it is an experience I want to fully own. It's also part of my healing. Nearly 7 years at Google was an incredible opportunity for me and I was fortunate to have wonderful teammates and a manager that fully supported me through these last few months. Thank you.
Fired by Google for Creating the Google Workspace CLI
Why This Matters
This story highlights the tension between innovation and corporate resistance within tech giants like Google. The creator's experience underscores how internal fears of disruption can lead to suppression of grassroots tools, which may hinder progress and user-driven innovation in the industry. For consumers and developers, it emphasizes the importance of open platforms and the risks of corporate gatekeeping.
Key Takeaways
- Grassroots tools can gain rapid popularity and challenge corporate narratives.
- Internal resistance to innovation may lead to suppression or termination of creators.
- Open-source projects and community-driven development are vital for technological progress.
Get alerts for these topics