Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Fired by Google for creating the Google workspace CLI

twitter.com

Post reply on HN
Print view View original

331–340 of 472 posts

Re: Fired by Google for creating the Google workspace CLI

#331

Post by yardsold »

justinwp wrote: post #269
anon84873628 wrote: post #86

Earlier quoted context omitted.

Straight from that page: >This includes side projects that have not gone through IARC, even for DevRel engineers. So did you do this "Launcher2" or "Ariane" thing and get the approvals? If so, it seems your ass would be covered. If not... I can sympathize that the process seems convoluted and could particularly bite a DevRel accustomed to more autonomy. One would hope Google would do the whole blame free retrospectiv…

Yes there was a launch with eng bit flipped by manager.

what is this bit flipping shit you keep alluding to?

Re: Fired by Google for creating the Google workspace CLI

#332

Post by KennyBlanken »

It's amazing the number of people (many of whom claim to be Google employees past or present) who probably consider themselves smarter than everyone else in any room they walk into...

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

https://news.ycombinator.com/item?id=48655744

Re: Fired by Google for creating the Google workspace CLI

#333

Post by olalonde »

qmarchi wrote: post #168
cdata wrote: 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…

Former Googler here, and one that has open-sourced projects while working in Cloud. This is certainly not the case in other product areas and for specifically for something that uses the Google name. If I was expected to go through a full IARC committee in order to get my little Discord bot open sourced under my own account, something that uses the Google name would likely have to get IARC + Legal approvals, along wi…

It's weird that he even had the ability to create public repos inside the official Google Workspace org then. That said, I agree that some information seems to be missing. Like, why not instead fire the guy who announced the project on X and who I presume is his manager? Confusing.

Re: Fired by Google for creating the Google workspace CLI

#334

Post by KennyBlanken »

fg137 wrote: post #139
justinwp wrote: post #114

Earlier quoted context omitted.

You are assuming that it was "personally" releasing something and that the process wasn't followed.

Why isn't it under google's username on github? Why does the repo say "This is not an officially supported Google product."? Is it actually approved by Google or not? You need to actually answer these questions instead of dodging them.

The reason you think he's "dodging" the questions is because you clearly don't know anything about the situation, like the fact that it was published under the github organization used by the workgroup he was in, same as a lot of other software the group authored.

Re: Fired by Google for creating the Google workspace CLI

#335

Post by dude250711 »

qmarchi wrote: post #168
cdata wrote: 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…

Former Googler here, and one that has open-sourced projects while working in Cloud. This is certainly not the case in other product areas and for specifically for something that uses the Google name. If I was expected to go through a full IARC committee in order to get my little Discord bot open sourced under my own account, something that uses the Google name would likely have to get IARC + Legal approvals, along wi…

> ...likely leading to significant internal confusion...

Bonus-promotion disruption.

Re: Fired by Google for creating the Google workspace CLI

#336

Post by neya »

LoganDark wrote: post #284
neya wrote: post #281

Earlier quoted context omitted.

> First: you ought to disclose that information when commenting on a topic that relates in some way to your financial incentives. I've never ever seen anyone, especially Apple shareholders disclose this here whenever they brush off something Apple did with malice - Eg. slowing down users' phones, spying on their siri recordings, etc.

Throttling is to avoid overloading degraded batteries. Replacing the battery alleviates the slowdowns. Apple didn't want your phone to shut off at 15% when the battery can't supply enough current to sustain full performance. Siri recordings are only ever stored to improve Siri. Apple does not share personal data or recordings with advertisers. There was a lawsuit based on coincidence alone. I am not an Apple sharehol…

> Siri recordings are only ever stored to improve Siri. Apple does not share personal data or recordings with advertisers. There was a lawsuit based on coincidence alone.

https://www.theguardian.com/technology/2019/jul/26/apple-con...

    Apple told the Guardian: “A small portion of Siri requests are analysed to improve Siri and dictation. User requests are not associated with the user’s Apple ID. Siri responses are analysed in secure facilities and all reviewers are under the obligation to adhere to Apple’s strict confidentiality requirements.” The company added that a very small random subset, less than 1% of daily Siri activations, are used for grading, and those used are typically only a few seconds long.
> Apple didn't want your phone to shut off at 15% when the battery can't supply enough current to sustain full performance.

That's what they told you to believe. Every other manufacturer also had smartphones with batteries at the time and they were not doing this FYI. That was just marketing speak by Apple. Please stop citing marketing speak.

This is not the core issue, though. The core issue is not disclosing financial incentives while commenting something positive / negative.

Re: Fired by Google for creating the Google workspace CLI

#337

Post by msephton »

jrochkind1 wrote: post #137
pydry wrote: post #135

Earlier quoted context omitted.

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.

> but yea it's true he didn't dot the i's and cross the ts. How do you know that's true? Do you have information the rest of us don't?

He probably read the twitter thread, it's all in there

Re: Fired by Google for creating the Google workspace CLI

#338

Post by [deleted] »

morpheuskafka wrote: post #307
jedc wrote: post #258

Earlier quoted context omitted.

It looks like the account where this repo was published was the one used by Google Workspace DevRel? (And that’s the team this guy worked on.) That makes this quite a bit different situation than publishing the repo on a personal account.

> getting grilled by legal about why the Google logo and brand colors are on the Google Workspace GitHub code repositories. The wording is very ambiguous, but to me it suggests the opposite. If legal was question why the logo was on the account profile picture, not just that specific repo's content, that would imply the entire account was unauthorized, right?

[deleted]

Re: Fired by Google for creating the Google workspace CLI

#339

Post by fragmede »

hilariously wrote: post #26
fragmede wrote: post #22

Earlier quoted context omitted.

Yes, berating a coworker for being a fucking moron is unacceptable in corporate America.

The truth is that in decent workplaces we've figured out attacking people doesn't generally get what you want, unless what you want is to have a tantrum. Calling an idea nonsense is fine, calling it not profitable is great, and saying its a waste of time is a Monday. Attacking someone as a fucking moron is pointless, just fire them, deprioritize them, or move on.

It's a reframe for

    > you can get punished at google (up to and including termination) for raising your voice in a meeting.
That makes it sound like Google is really weird for firing people for merely "raising your voice in a meeting", but the reality is that toxic assholes who can't control their emotions and yell racist slurs at people do get fired, but, uh, shouldn't they?

Re: Fired by Google for creating the Google workspace CLI

#340

Post by stevage »

etothepii wrote: post #293
stevage wrote: post #272

The text of their "tweet that got me fired" is: > Introducing the Google Workspace CLI: https://github.com/googleworkspac e/cli - built for humans and agents. > Google Drive, Gmail, Calendar, and every Workspace API. 40+ agent skills included. Yeah, that absolutely looks like an official product announcement from Google. Surely it was obvious they'd get in trouble for that.

Is the issue primarily caused by the English language? (Google Workspace) CLI vs Google (Workspace CLI) Because Google has there name in the product for which the CLI was produced it looks like he's using the Google brand when he's only using a descriptor of what his CLI was for. Trademarks are funny, but if I build a thing that only works with Google Workspace wouldn't it be a bit weird to not say that?

Good point. "CLI for Google Workspace" would be less ambiguous.
Post reply on HN