alt Hacker NewsThe concerns seem to be primarily around trademark and logos? Unless there's more to it, those seem trivial to remedy by requiring removal of logos and renaming in the style of Clawdbot -> Moltbot -> OpenClaw. Google is well-known to be pretty sparing with firing people even for performance, so either this is a change in stance (entirely possible) or there's more to it.
Replies
I think that’s a good instinct but this line…
“I think the cause was that Workspace and certain leaders (and projects) were afraid of being disrupted.”
Suggests that there is much more to it. I suspect it’s actually about disregarding Google’s internal processes (which is forgivable) and then demanding to work unilaterally (unforgivable). The amount of positive feedback may have given the author too much confidence that he could dictate to leadership what comes next.
A Google Workspace CLI is a useful project idea but it isn’t groundbreaking, it’s something that the Google Workspace team should be involved in. I suspect he just wanted go steamroll over them. Shipping stuff in a team is never about just producing the code.
For over the last >1 year, Google has been dismissing people without warning or cause. The days where it was nearly impossible to be fired are over; now you might be severed by surprise for no given reason at all.