Posted by justinwp 2 days ago
tasting the rainbow
> 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.
Seems to me your management chain was thinking “Why the hell is someone on our team releasing a vibe-coded CLI that’s branded to look like an official API, when we’re 2 weeks from announcing the actual CLI??” If you didn’t know there was an official CLI in the works, that’s one thing, but if you did know then that’s pretty shitty to your teammates in Workspace and bad for users who would adopt one CLI (thinking it’s official) just to then see another one 2 weeks later.
Still, I would expect a talking-to and not an actual firing… but who knows what actually happened since you’re not responding to anyone. :shrug:
I'm not really implying -- I'm stating that I don't think his management chain was "afraid of being disrupted", but that they were pissed that one of their own team members released a product with Google branding that was the same thing they were about to announce in 2 weeks. It was poor judgement. Not worth a firing, though, in my opinion.
Market validation can change roadmaps. As I stated on Twitter/X, CLIs for agents was not a very interesting thing outside a small group earlier in 2026.
...who did not figure out that this project was published in a google-run github org, it was approved by his manager, etc.
As he has said multiple times: he went through the publishing process with his manager's blessing. Stop making up bullshit about how he didn't follow processes.