Behavior like grabbing a strangers crotch from behind and disappearing before she has a chance to turn around "works"?
No, it most certainly does not. There is a big difference between being confident and showing leadership, and groping strangers in public.
And the "agressive, alpha male" (which is a term that I hate, by the way) persona doesn't work for everyone, either. I know plenty of women for whom that's a huge turn off.
> It's almost as if when the girl is attracted to the guy, it's flirting, but when she isn't, it's creepy/sexual harassment.
It's creepy and harassment if it's creepy and harassment. You can flirt without grabbing someone's crotch, without trying to lick them without permission. There are also more appropriate venues for flirting, and less appropriate venues. At a hacker conference, people are generally more interested in talking about hacking and less about flirting; and in particular, there are many women there who will already feel a little ill at ease and marginalized due to how few of them there are relative to the men, who might not take kindly to many people treating them more as a potential date than a peer. At a singles bar? Flirting is probably more appropriate.
And yes, there is a certain degree to which some behavior will be interpreted as flirtation by some people and creepy by others. To avoid that, it's good to try to cultivate a certain sense of self-awareness, and when in doubt, err on the side of not being creepy.
> At a hacker conference, people are generally more interested in talking about hacking and less about flirting;
Even if I were trying to pick someone up at a conference, I'd talk about hacking, engage their interests, ask them what they are working on, etc. Intellectual flattery.
Physically, I'd be cool. If, after some time, the woman initiated some innocuous physical contact (shoulder & arm touching, for example), I would not reciprocate in kind. No, I would reciprocate with more platonic interest. This might be slightly disappointing at first, but it would build trust. Physical reciprocity only later, like a long-delayed echo.
Really, the physical stuff is entirely dispensable in the courtship phase. So is any kind of sexual innuendo. Keep it cerebral, boys. Ask questions, listen.
"If, after some time, the woman initiated some innocuous physical contact (shoulder & arm touching, for example), I would not reciprocate in kind. No, I would reciprocate with more platonic interest. This might be slightly disappointing at first, but it would build trust. Physical reciprocity only later, like a long-delayed echo."
At which point she would think you aren't interested in her and then move on mentally and physically to someone else.
Yeah, I'm having to fight really hard to continue giving the language a shot after seeing that syntax. Let's see, from their Dining Philosophers example:
[]{
Already, the syntax is starting to look a little strange, but OK, I'll give it a shot.
id = [int\];
Hm. Backslash seems to be used for something other than escaping. Not a good sign.
=;
Huh? The equals operator is being used alone, with nothing on either side? That's really stretching the bounds of convention.
-> --> <-> <-
We have various types of arrows that are used as syntax. In some cases, they're used as binary operators, in some cases as unary. Doubling up of dashes appears to change the meaning. This is really not looking good.
And then there's the example you mention. Besides how it looks; their example of solving a useful concurrency problem is "a bug-free, efficiently multithreaded real-time clock + infix calculator hybrid application"? Why would you even want that?
There may be something interesting here, but between their quite bizarre syntax and poorly chosen examples, they aren't doing a very good job of hooking me.
Hm. Backslash seems to be used for something other than escaping. Not a good sign.
From the tutorial[1]:
In ANI, \ means "latch". Basically, a latch is a place where you can "hold on to" an object of the specified type. A latch is like a box that you can put things in to, take things out of, and peek at what's inside.
If it weren't for the long-running convention of using backslashes as escape characters, postfix backslash would make some kind of sense, at least visually.
Forward slashes are for prefixes, backward slashes are for postfixes. Nice parallel there :)
Aside from breaking the escaping convention, slashes in code give the page an unfortunate swirly quality. It seems like line other parallel or perpendicular can make the line of the page look it is at a different angle.
Myth 1 is completely false. While companies will be careful about what they have summer interns write, they are absolutely expecting to get real value out of the intern's work. They are spending both money, and the time of the mentor(s) on the intern; do you think they are doing that for charity? Yes, you need to plan for the case that the intern doesn't successfully complete their project; that's why you have things like revision control and code review, to ensure that they don't do more harm than good, and you don't give them a project that absolutely needs to be completed by the end of the summer. Though at most places I've been, there has been more than enough urgent, mission-critical work that the existing developers couldn't possibly finish, so some of it does go to interns as it's not like the existing developers would have gotten to it in that time anyhow. I am mentoring several interns right now, and their code is shipping to customers already, in a core, mission-critical component of our stack.
Myth 2 is something that I'm sure that no one believes. Sure, people try to pick out reasonably scoped and specced projects for interns to work on, just as they do for anyone to work on, but that doesn't mean that they succeed, and I can't imagine that anyone would expect perfection. Furthermore, dealing with ambiguity, changing specs, scope creep, and the like is part of the value of the internship; you're going to have to learn how to deal with that eventually.
Myth 3 is about the only good point of advice here. It is difficult for a mentor to provide enough time for their interns. They usually have a variety of other things to do. But the interns won't be very effective if they sit around stuck waiting for help. Being assertive, and asking for help when you're stuck, will allow you to get a lot more out of an internship than just sitting around waiting for someone to mentor you.
The big problem here isn't detecting bots. Sure, in this one company's case bots may be the problem; but in general, it's detecting behavior that you are paying for that doesn't make you any money. There may be real users who click "like" a lot; they may do it because they're paid, or they may do it because they're bored and trying to see how many "likes" they can collect. It doesn't really matter; none of them are very valuable to an advertiser.
Rather than trying to explicitly filter bot traffic, they should try to quantify the value of particular "likes". For instance, a user who demonstrably clicked through and purchased something is much more valuable than one who "likes" 10,000 companies and has no friends, whether or not they're a bot.
And heck; a bot that has thousands of followers who all buy lots of things is valuable too. Maybe someone created a particularly effective meme-generator bot, and people who follow that bot are likely to buy ironic T-shirts. Whether or not a user is a bot isn't all that relevant; it's whether that user's activity correlates with you making sales.
So, shouldn't the protocol involve the client generating the order ID, so that they can cancel the order without having yet gotten confirmation of it? Or at least, the client being able to include a "client handle" for this purpose, that is independent of the order ID but which they can use to refer to it before they've gotten the ID?
Or have it do some high level of QOS where both sides need to acknowledge that the other side received the message otherwise cancel the request. This is pretty much what TCP does.
But toys aren't necessarily for kids. There are many toys which are intended for adults. Now, in some cases they may be called things other than toys (fashion accessories, schwag, sports equipment, sex toys), but at their heart, they are toys, just toys targeted to adults, not kids. Should every one of those that's dangerous be banned because it might be mistaken for a toy for a kid? Does the fact that a vibrator or handcuffs are sold as "sex toys" mean that they should meet all of the safety guidelines for children's toys?
Or should we say, maybe, that people should just exercise better judgement themselves; that people should realize that a collection of many small round magnets that are easily lost and difficult to do anything with without some fairly fine manual dexterity probably isn't the best toy for someone who might be tempted to eat them?
Agreed, but BuckyBalls look very harmless to most adults and kids (they're basically beads), so most people don't put much care into hiding them from young kids.
Trivial way to defeat the timing attack: Don't do anything but enqueue the request before returning to the user. Process the request and send the email asynchronously. Which you should be doing anyhow; you're not going to wait for the email to send successfully before displaying the message, are you?
I found this article more informative than Elements of Style. Elements of Style is full of poorly thought out grammatical "rules" which are flat out incorrect, or over-generalizations without much guidance on how to properly apply them, and even the authors of Elements of Style don't actually follow most of their own "rules." If you actually tried following Strunk and White's rules, your writing would come out sounding bizarre and stilted.
The thing is, the vast majority of this isn't needed by most applications. For instance, in a database, all they need is to encode and decode strings properly when going to or coming from external sources. That's all that is being asked for here; that when MySQL says "UTF-8", they really mean "UTF-8", not some broken subset of it.
No, it most certainly does not. There is a big difference between being confident and showing leadership, and groping strangers in public.
And the "agressive, alpha male" (which is a term that I hate, by the way) persona doesn't work for everyone, either. I know plenty of women for whom that's a huge turn off.
> It's almost as if when the girl is attracted to the guy, it's flirting, but when she isn't, it's creepy/sexual harassment.
It's creepy and harassment if it's creepy and harassment. You can flirt without grabbing someone's crotch, without trying to lick them without permission. There are also more appropriate venues for flirting, and less appropriate venues. At a hacker conference, people are generally more interested in talking about hacking and less about flirting; and in particular, there are many women there who will already feel a little ill at ease and marginalized due to how few of them there are relative to the men, who might not take kindly to many people treating them more as a potential date than a peer. At a singles bar? Flirting is probably more appropriate.
And yes, there is a certain degree to which some behavior will be interpreted as flirtation by some people and creepy by others. To avoid that, it's good to try to cultivate a certain sense of self-awareness, and when in doubt, err on the side of not being creepy.