3 ms·
> It seems more like he misunderstood the necessary steps before making that release. Dude worked there for 7 years. Saying "oh, he just didn't understand the
by hn_throwaway_99 4mo ago
> It seems more like he misunderstood the necessary steps before making that release.
Dude worked there for 7 years. Saying "oh, he just didn't understand the policy for going through legal/management approval" just does absolutely not pass the sniff test.
- whstl 4mo agoPlus there are 57 projects in that workspace from the same team, most using the same API, in quite a few the fired dev is participating. On top of that, the CLI project wasn't even deleted. If there were/are real problems there, Google hasn't acted on them in any proper manner, and has not communicated properly with any of the parts involved, which is natural when legal/HR is involved.
- pydry 4mo agoThis is definitely helps make the case that it was a spiteful exec primarily concerned with their own fiefdom that got the guy canned. I did think when the guy released the tool that it seemed a bit out of character for google to be that responsive to customer feedback.
- cromka 4mo agoThere's a small chance they actually still don't get it and that blog post is just a testimony to how unfairly hurt they feel.
- PurpleRamen 4mo agoPolicies change or have subtle context-specific details. Even after 7 years, people can lack basic knowledge for certain situations.