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

461–470 of 472 posts

Re: Fired by Google for creating the Google workspace CLI

#461

Post by whstl »

magicalist wrote: post #430
whstl wrote: post #291

Earlier quoted context omitted.

If that's a real problem and fireable offence, then there's people at Google that should be fired ASAP for failing to delete this repository.

> If that's a real problem and fireable offence, then there's people at Google that should be fired ASAP for failing to delete this repository. Unclear what you're referring to here. Was it "misrepresented what they would be releasing"? If that's the case, I disagree that the repo still existing is on its face evidence against that theory. It could be a perfectly fine tool, but if you lie on a release checklist, depe…

It's either a problem to have this released or not. Google doesn't seem to care this is in an official repo.

> its also speculation to suggest that's the only reason he was fired

That's the reason given by Google.

The implication here is that Google is lying about this whole thing for ass-covering reasons.

People here are up in arms because someone potentially misrepresented a tool that Google itself doesn't even care to remove, while Google HR and legal are possibly lying to damage someone's livelihood.

Re: Fired by Google for creating the Google workspace CLI

#462

Post by xnx »

jofzar wrote: post #222
djeastm wrote: post #110

Earlier quoted context omitted.

He seems to be a good coder with poor judgment. But I think it would be wiser to manage him better than to fire him so long as he recognizes what he did was wrong. I'm a bit of a softie for the clueless, brilliant coders, though.

My bet is that he was reprimanded for this and then didn't back down, hes even in the comments here now arguing about it

Bingo. There's lack of detail about the original circumstances, but behavior since points to what the problem was. A lot of times you start the discipline process for a rogue employee and then become even more certain about the decision.

Re: Fired by Google for creating the Google workspace CLI

#463

Post by xnx »

jrochkind1 wrote: post #438
argee wrote: post #194

Earlier quoted context omitted.

As a Xoogler you should know that the "impact" they want is, making leadership look good, what you shipped or even whether or not you shipped is nigh irrelevant. This did the opposite, didn’t it?

I don't see anything about the product that made Google leadership look bad? I don't see that anyone else external to Google thought so either, before they fired him? Firing him makes them look bad, however.

Shipping a personal project right before they were going to announce an official tool at Google IO seems like a bad idea.

Re: Fired by Google for creating the Google workspace CLI

#466

Post by msephton »

jrochkind1 wrote: post #452
msephton wrote: post #448

Earlier quoted context omitted.

The twitter thread was more than enough for me to understand what has gone on.

Are we talking about the same twitter thread? This one? https://xcancel.com/JPoehnelt/status/2069482265953087602

Right, but a single link is not enough as there are many off-shoots on the thread (it's not linear); other Google employs chime in and all sorts of other info.

Re: Fired by Google for creating the Google workspace CLI

#467

Post by waterTanuki »

ventana wrote: post #396
waterTanuki wrote: post #176

In the README > This is not an officially supported Google product. Why was this project published under an account named "Google Workspace"? Google seems to want to have their cake and eat it too, same with the cli creator. If you want to publish a project under open source and you are the sole creator/owner -> do it in your own time, under your OWN individual github account. Nothing good has ever come from ceeding…

Xoogler here who also published things within Google repositories. This is a standard phrase that you should have in the README to get an approval to publish your repository to GitHub, even if it is totally related to the Google business (as mine were). My guess is that it's similar to the regular "no warranty" clause in the licenses, just explicitly opting out this code from any possible agreements Google might have…

The issue isn't lack of documentation, it's the policy itself. If it's not supported by google it shouldn't be published under their name. Simple.

Re: Fired by Google for creating the Google workspace CLI

#469

Post by jrochkind1 »

xnx wrote: post #463
jrochkind1 wrote: post #438

Earlier quoted context omitted.

I don't see anything about the product that made Google leadership look bad? I don't see that anyone else external to Google thought so either, before they fired him? Firing him makes them look bad, however.

Shipping a personal project right before they were going to announce an official tool at Google IO seems like a bad idea.

So it was done on the clock as a project at Developer Relations team, I don't know if that should be called a personal project or not, maybe, it does seem Developer Relations projects could be one person's idea and execution, but just to be clear on what happened.

It was released 2 and a half months before Google IO.

The way I read this, they decided to announce it at Google IO because of the attention the project released by the Developer Relations team got. No one with inside knowledge has said the "official tool" (not from Dev Relations) was already planned when it was released. Maybe it was. Maybe a guy on the Dev Relations team would or should have known it was if it was. Easy for me to believe it was not however.

Post reply on HN