I think there's still something to be said for professionalism. I curse like a sailor when frustrated (which, as a coder, is about 95% of the day) so I constantly have to rein it in. This is because avoiding offending people does matter.
If you want to have an open and inclusive environment, you have to keep in mind the terrible things you say. You want to attract a group of top and diverse people? Some of those folks are going to have thin skin, or they're going to have sensitive buttons that you don't have.
They can't avoid hearing it, but you can avoid saying it.
And as for rude code? I've got a team under me now and I've seen it happen already a few times: somebody will see it. I don't care where you wrote it, it will be seen. Murphy's law just works that way. Your IDE will be open when you remote in to fix something during a rough alpha-stage demo, or a variable name will become a database column will become a column of a report.
Somebody will see it, and they will be offended, and it's your ass.
If they're offended, they're performing ego driven development. Aim cursing at the code, not the person: "This code is complete horseshit" means exactly that and one's got room for improvement, not that one is worth complete horseshit.
I'd rather have people around me that have the courage to say "WTF is this shit" rather than the politically correct talk about how this code "will not work" and could be "improved". In my current situation the latter only leads to wishful thinking ("in an ideal world we'd fix that... later") and handwaving of my "academic" thought process. Yes it's my ass, the one ass that's sick of making up for people mistakes all the time, and the only thing that has a semblance of snap them out of their numbness is to shock them.
There is nothing less professional than shipping non-functional code to customers, nor imposing undue amount of work to your teammates by writing an unmaintainable mess, either of which being more equivalent to a giant implicit "fuck you" than colourful words.
If you want to have an open and inclusive environment, you have to keep in mind the terrible things you say. You want to attract a group of top and diverse people? Some of those folks are going to have thin skin, or they're going to have sensitive buttons that you don't have.
They can't avoid hearing it, but you can avoid saying it.
And as for rude code? I've got a team under me now and I've seen it happen already a few times: somebody will see it. I don't care where you wrote it, it will be seen. Murphy's law just works that way. Your IDE will be open when you remote in to fix something during a rough alpha-stage demo, or a variable name will become a database column will become a column of a report.
Somebody will see it, and they will be offended, and it's your ass.