Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In every failed relationship there are two sides. Maybe one is entirely at fault, maybe the other, maybe both share blame of maybe there's just a basic incompatibility. This is true for work just like it is for marriage.

In each case, it is easy for one to point out flaws in the other. And in some cases, "the other" is the only one that has flaws. But in most cases it is probably a combination.

Just because a company has culture issues doesn't mean that every employee is blameless or perfect. When someone doesn't work out for a job it is hard to disentangle how much of the blame belongs on each party.

In this case, I'm fairly familiar with a lot of the facts on the ground. As I said above the article makes a good critique of the real problems Google has. But it also blames some of those problems for mistakes/failures the author himself made (in my opinion).



You make good points. I'm not in a rush to ascribe blame to anyone. It's just that sometimes certain culture prompts people of certain mindset to make certain mistakes. Repeatedly and predictably. Is the culture to blame, or is that person to blame (each and every time)? And is it productive to even use the word "blame" in this situation, or should other concepts be used?

Since you're more familiar with the facts of the case, I can contribute nothing more than to offer a different angle to look at this.

And I'll leave the author's self-improvement journey to the author.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: