Live data from Hacker News

Fired by Google for creating the Google workspace CLI

twitter.com

141–150 of 472 posts

Re: Fired by Google for creating the Google workspace CLI

#141
post #131

I'm noticing a few commenters who work (worked?) at Google (inferred from comment history) who are critical of this person's actions. First: you ought to disclose that information when commenting on a topic that relates in some way to your financial incentives. Second: when I worked at Google under Chrome it was very common for individuals and teams to publish projects to open source repositories under Google-managed…

Used to be part of Google’s culture until the AI wars and walled garden present we find ourselves in.

Re: Fired by Google for creating the Google workspace CLI

#142
post #131

I'm noticing a few commenters who work (worked?) at Google (inferred from comment history) who are critical of this person's actions. First: you ought to disclose that information when commenting on a topic that relates in some way to your financial incentives. Second: when I worked at Google under Chrome it was very common for individuals and teams to publish projects to open source repositories under Google-managed…

So is it normally allowed to publish a non-Google-affiliated repo under Google's brand? This seems weird to me, and I can't understand why he didn't just do it under his own name.

I did work at Google until a year ago, when I quit and sold my stock, but not in a team that remotely deals with open source so idk how this works.

Re: Fired by Google for creating the Google workspace CLI

#143
post #135

Earlier quoted context omitted.

It sounds like a big part of why he was let go is that he created a work-related product, possibly using his '20% time' meaning he created it while at work, and then released it with Google branding and logos, all of which without clearing it with anyone at the company, while his name is attached to the company. In other words, he created an extremely official-looking product and released it in a way that made it loo…

Struggling to see how google was harmed by this but yea it's true he didn't dot the i's and cross the ts. I actually thought when it was released that it was a pretty clever move by google in a sea of bad decisions but they've cleared that misapprehension right up.

As a customer and dev, it's confusing to me when I look at Google's stuff and see official-looking unofficial CLIs.

Re: Fired by Google for creating the Google workspace CLI

#144
Yes. While they may have been justified in firing him for not following policy, they also lost a talented engineer. (I'm sure they don't care) I would have done the intelligent thing here and looked at how the project could have been made official. But that decision would have had to been made at a very high level, maybe even the CEO, because anyone lower down would have made a narrow and parochial decision in favour of the org they were protecting, rather than in the best interests of the company.

Re: Fired by Google for creating the Google workspace CLI

#145
post #14

The 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.

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.

It's both. They're usually more lenient than other companies when it comes to performance, but then there are random waves of layoffs that have more to do with what org you're in than anything else.

Re: Fired by Google for creating the Google workspace CLI

#146
post #40

Yikes. The lack of judgement involved in personally releasing something that could be confused for an official release (I was confused) by your employer is someone who has huge wildcard risk in the future. I would expect significant disciplinary action if they didn't follow procedure, and termination if they were directly warned at any point.

Yeah this is super weird to me, because the processes at Google for employees to release and attribute ownership of open source projects are extremely clear and well established. It's genuinely hard for me to imagine this happening in a way that confused or caught the author off guard. It's totally fair to question the wisdom of those processes and policies! But I'm pretty skeptical of the "I'm surprised I got in tro…

Clueness sometimes goes hand-in-hand with perceived freedom. I think it's that cause and effect are not as often connected (consequences). I remember a Google employee updating a Google font that broke thousands of websites. Community members explained that Google recommended (at that time) letting Google host the font, and that they could fork it instead, or find a path that wouldn't break so many websites. The employee took the implication of consequences as being connected to ther actions as an aff(r)ont "They can just host it themselves"; "they can switch to another font/redesgin their site". When it was pointed out that the cause would not be known to most, and that budgets would have to be found to ferret out the cause and implement the solution, etc., etc., the Google employee stopped responding.

Re: Fired by Google for creating the Google workspace CLI

#147
post #15
post #11

I don't get it – you called the GitHub org 'googleworkspace' and used the Google logo? Presumably without permission? Don't Googlers regularly open-source side projects under the official org(s)? Did you really think this was going to be fine, or was it 'growth hacking' with tougher consequences than expected?

I believe it's an official or semi-official Google github org. Typically at Google there is some process you are supposed to follow when opensourcing your code, and a repo like this exists specifically to get more people to use the API. The CLI still exists at the repo and the repo still has the Google branding, so it's 99% certain this is a Google repo. If you do an end-run around the normal open source publishing y…

How come it's not under "google" organization, which is where almost every other Google open source project lives (with the exception of a few notable ones)? That's just weird.

And if you look at the history, the main maintainer for the project was really just one person.

Even today, the repo clearly says "This is not an officially supported Google product." So what is this?

If you told me the "googleworkspace" account is owned and controlled by this individual, not Google, I would have believed it.

Re: Fired by Google for creating the Google workspace CLI

#149
post #122
post #49

Earlier quoted context omitted.

I've never worked for an employer, from pizza delivery, to corporate intern, to multiple startup, to FAANG, that didn't have this VERY CLEARLY worded in the employment agreement, right up top: 1. Any work you do during company time/resources/equipment, is company property. 2. Anything public related to work, or that could be considered as competing or providing the service in the same space as work, needs to be vette…

The policy was always crystal clear, but at the same time, tons of people found it confusing. "I wrote this at home on my personal computer in my free time? Why does google own it? how can that be legal" came up a lot. People would get into huge fights with OSPO over this.

> "I wrote this at home on my personal computer in my free time? Why does google own it? how can that be legal"

Interesting. Did they read their contract before signing it?

Re: Fired by Google for creating the Google workspace CLI

#150
post #45

Earlier quoted context omitted.

Google is worth $4+ TRILLION. There is natural and needed bureaucracy in preserving that. This type of probably well-meaning, but cowboy activity is not worth the risk to Google.

Sounds like exactly why they're now a lumbering ineffectual beast, rather than the center for innovation that they used to be.

It depends on what you consider ineffectual to mean. Ineffectual at making new products and innovating? Yes, definitely. Ineffectual at preserving business momentum and continuing to grow profits? Well, the latest numbers speak for themselves.
Post reply on HN