I'm not sure if you do, honestly. The point of the exercise is exactly the ambiguity that stood out to you.
Also, the question was very explicitly not asking if an ambulance in the park is "okay." The question is asking is it a rule violation.
It's an excellent analogy, in my opinion, because what it's trying to be analogous to is the general ambiguity of language that makes content moderation difficult. It's hardly even an analogy because it is about precisely an identical concept: determining whether behavior is violating a rule.
You and antihero are talking about two different kinds of "good listening," though.
"Being a good listener" has both a practical and a social component. You are referring to the social component ("in Japanese culture..."). The tenets of social interactions in Japanese culture which have been ingrained in speakers of the language to one extent or another. The performance aspect of the act of listening.
antihero is talking about the practical form of "good listening" when they say "that makes you a terrible listener though." That is, what is the function of "listening" in a social interaction? I would hazard a guess that they believe the function of listening is to understand what another person is saying.
And by that benchmark, an individual who is not actually reaching any sort of understanding is a "bad listener" irrespective of how successful they are at performing the cultural/social component of the act of listening.
There's the additional implication that because signaling you are understanding when you are not leads to misunderstanding (which is the antithesis of the intended function of listening), it makes the listener an even worse quality listener than if they were not performing.
OP was not suggesting that search engines cannot be used as a tool in the process of taking the test. Rather, that your test should not be something which a candidate can Google a pre-existing solution to and submit as their own.
While I agree with both sentiments, I find the juxtaposition between the two interesting as it implies a relationship between them but they don't seem to be related at all.
>...he should seriously consider putting more effort into the documentation and distribution side.
In addition to what other people have said, Blow is explicitly working on documentation over time and closed beta users have access to a fair number of documents detailing both language features and the philosophy behind the language.
One huge reason why the language IS still in closed beta is because Blow believes heavily in not releasing half-assed work. Documentation is a part of that.
"This version of the sentiment which you did not express is totally reasonable, therefore it seems nuts to hate people for the sentiment that you DID express."
I would imagine it's because WSL is a terribly confusing name itself for a lot of people.
There are two ways to read "Windows Subsystem for Linux":
1. This is a subsystem that runs on Windows that enables Linux binaries.
2. This is a subsystem that runs on Linux that enables Windows binaries.
The confusion comes in the fact that when I write those two sentences, I naturally want to write "This is a subsystem FOR Windows..." or "This is a subsystem FOR Linux... ." I had to consciously avoid using "for" in that sentence to highlight the problem.
So when someone who doesn't know what the thing does reads "Windows Subsystem for Linux" they may walk away with the false impression that the subsystem allows Windows binaries to run on Linux. Likewise, what you're seeing now is that people are seeing "DOS Subsystem for Linux" and thinking that this enables you run DOS on Linux.
It seems like a lot of the discussion surrounding DOD that gets popular interest is centered on a small set of patterns that you can apply. And the implication that DOD is the application of these patterns usually follows.
Taking this article as an example, it frames DOD as an optimization technique and explicitly states that these patterns are the main concepts of DOD.
But while these patterns are interesting and often show up in data-oriented designs, they are not themselves foundational to data-oriented design.
This is interesting to me because it seems to obviously be missing something. If the article went through a list of the design patterns present in the GOF book and framed them as the main concepts of OOP, I would imagine people would be a little bit suspect, right?
That's because it's kind of the reverse, isn't it? The main concepts of OOP may result in certain common PATTERNS of code structure and layout -- which have usually been given names like "Strategy" and "Visitor" and "Singleton" -- but those patterns are not themselves the main concepts of OOP.
Likewise, data-oriented design might lead you to convert an array-of-structures into a structure-of-arrays or avoid branching on a hot path but those patterns are not themselves DOD.
>Not to be dismissive, but this post feels a bit like rambling without a clear thesis or main argument.
The post opens with:
>This is more of a brain dump or an internal monologue. I don’t intend to prove any point or convince you to start your own thing. Neither do I want to reassure you that working for someone else is the best option for most people. My goal here is simply to get my thoughts out so I can think clearly again and rationalize this thing that’s been nagging me.
IBM's response to Google called "On 'Quantum Supremacy'" has this to say:
"Because the original meaning of the term “quantum supremacy,” as proposed by John Preskill in 2012, was to describe the point where quantum computers can do things that classical computers can’t, this threshold has not been met."
In other words, "quantum supremacy" is not being used as just a buzzword.
So yeah, IBM is casting doubt on Google's claims of "quantum supremacy" because "supremacy" doesn't just mean "better than everything else."
Not OP, but...the advent of cars over horse-drawn carriages involved a _lot_ of deaths before both pedestrians and drivers learned. There was also a lot of propaganda put out by car companies to change the popular conception of roadways from being a place where people walk and children play to being a place for cars. [1] So...it's actually pretty close to people needing to be told to look both ways.
I think that what you are saying here doesn't necessarily serve as a counterpoint to the GP's point. Rather, it's only an additional piece of evidence. Where GP referred to things like a parent being sick serving as a downward pressure in the effort to improve one's circumstances the point is one of externalities which are not typically accounted for.
And in this case, the externality you're bringing up is that oftentimes being raised poor means you're being raised in an anti-intellectual environment. And that externality is something that a lot of poor people have to deal with.
It's another instance in which the game appears to be rigged against those from a poor background.
Software development does not have to be a stressful experience. I'm sorry that you believe it does as that implies that your experience has largely been stressful.
In my mind, that perspective is a huge red flag for me when I'm on the job hunt. If you are trying to stress me out in an interview rather than make me comfortable then I have to thank you for letting me know before I started working there that you would be exhausting both physically and emotionally.
The word fiancé/fiancée is gendered. It is one of the few gendered words in English, as the gender was not dropped in taking it from French. Fiancé refers to the male. Fiancée refers to the female. They are pronounced exactly the same, which is why you have never heard it.
Also, the question was very explicitly not asking if an ambulance in the park is "okay." The question is asking is it a rule violation.
It's an excellent analogy, in my opinion, because what it's trying to be analogous to is the general ambiguity of language that makes content moderation difficult. It's hardly even an analogy because it is about precisely an identical concept: determining whether behavior is violating a rule.