Google Workspace CLI and API Policy Violations
Getting fired for writing a successful tool is a weird way to find out where the line is between being a "proactive engineer" and a liability. Justin Poehnelt built a Google Workspace CLI, put it out there, and watched it hit number one on Hacker News. It gained thousands of stars and users in a matter of days. Then Google fired him. Most of us are told that shipping high-impact code is the fastest way to get promoted. But there is a hidden friction when your project goes viral outside the walls of your company. Suddenly, you aren't just a developer solving a problem. You're a security risk or a policy violation waiting to happen. It makes me wonder if the "owner mindset" we're all encouraged to have actually has a ceiling. At what point does taking initiative stop being a virtue and start being a fireable offense? The tool and the intent The goal of this CLI is to stop the constant context switching between the terminal and the browser. If y...