4 ms·
Well, the session was titled "The Ten Dirty Words And How To Use Them". If you sign up for a class about human sexual behavior, you shouldn't be offended when
by jonhendry 15y ago
Well, the session was titled "The Ten Dirty Words And How To Use Them".
If you sign up for a class about human sexual behavior, you shouldn't be offended when they talk about anal sex.
- ceol 15y agoAre you really equating signing up for a developer conference to signing up for a class on sexual behavior? If I take a class on human sexual behavior, I don't expect 80% of it to be dick jokes.
- jonhendry 15y agoNo, I'm equating a conference session, likely one of several running at the time, described in the title itself as involving "dirty words", to a class on sexual behavior. If you go to a session that says it involves dirty words, you really shouldn't be surprised or offended when it involves dirty words, or at least attempts at saucy double entendres. Admittedly, one might think "dirty words" wasn't meant so literally - perhaps it meant "words that describe things you shouldn't do, like 'over-release'". That ought to have been made clear in the conference materials.
- pyre 15y agoI think the real thing here is that if the entire point of the session is to make dirty programming jokes, does the content of that session really provide anything to the conference? I don't think many people go to conferences expecting it to be like a comedy club... Just sayin'
- alphakappa 15y agoWhen that is the stated purpose of the talk, then one has the option to avoid it. It doesn't seem fair to attend a talk that warns you of its nature, and then complain about it.
- jonhendry 15y agoI suppose it depends on the technical content. The session was pretty much using groan worthy euphemisms as a way of selecting a limited set of things to cover. That slice through the APIs may cover different things than other sessions that deal with more monolithic topics like 'Core Animation' or 'Core Data'.