Hacker News new | ask | show | jobs
by Arainach 35 days ago
Build cool shit and follow the proper release procedures for it. There is a huge difference between something unrelated to your employer on a personal repo, youremployerrepo/api-samples, and calling something "Employer Majorproduct CLI" on an official employer repo which is bound to be confused for an official release.

I would have been fired from every employer I've ever worked for of any size for doing something like that - including Google circa 2018.

2 comments

> follow the proper release procedures for it

What happens when your thing

or nothing close to your thing

will ever see the light of day?

1. If google said ok but don't release under google’s name/in google’s repo, do that.

2. If google said no this goes against our goals for the product, don't release it if you want to keep working for google?

It was clearly greenlighted by management. The person who made the announcement was Addy Osmani, who was manager of the fired developer at the time.

This is in a Google-owned organization, with several other similar repositories, a lot of them using the same API.

Looks like Addy Osmani is leaving, too.
Is that relevant here,

given that Google was creating an official thing

quite close to his thing

at the same time?

(And why are we writing like this?)

Fair to point out,

the official google thing,

was quite a lot worse

than his thing.

(I’m quite into the whole “Posting in free verse” idea)

Would you like them

in a house?

Would you like them

with a mouse?

AI am Sam ...

Sam AI am ...

My program made green eggs and ham ...

Is there a smell of toast burning where you are?
> Google was creating an official thing quite close to his thing

Just link to it.

It's mentioned in the original link for this post.
None of that is relevant. You're working on things for their employer, they control when and if anything is released. Most of us have worked on projects that were cancelled - even when that happens you don't just release it anyway.
> they control when and if anything is released

I don’t think that’s how APIs work at all.

Upon reflection, the only thing this guy did wrong was put his name on the thing…

>Build cool shit and follow the proper release procedures for it.

By all reasonable measures, they did.