Hacker News new | past | comments | ask | show | jobs | submit login

A lot of the time I agree. I don't think I've ever had a need to opine on the merits or demerits of the filibuster at work.

But "should we deploy in China, knowing we will have to hand over data on possible dissidents?" is something I've had to deal with repeatedly. I see no way of having that discussion without getting into politics.

Of course, you can rightly say that some people just sit down and write code without becoming embroiled in the great conflicts of our time. That's true.

But the struggle for diversity in tech and equality more broadly is one of the great struggles of our time, and I know of very few engineers who do not recruit, interview, or hire. Should those people just cash their paycheck, or should they take the time to discuss an issue that nearly all employers claim to take seriously?

I think you can continue with this line of reasoning to include things like compensation (especially health insurance, m/paternal leave, and sick leave policy). And nearly everybody has a stake in the compensation discussion.

So, while I get the desire to just do the work and go home, I don't think it's so easy to separate politics from work without doing grievous harm to both. Which suggests to me the obvious thing: that the real goal of these efforts is not to foster inclusiveness or provide a better working environment, but rather to prevent a dialogue about how to do just that.




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

Search: