levythe

Or even that it changes depending upon the container it's displayed within

IANAL, but in my opinion, a gun emoji is not a threat in any isolated context. There would need to be enough other context before I would consider it a threat that the emoji would be irrelevant compared with the other evidence.

I've had multiple take home tests result in changes to the products that company offers. I've never received a job offer from those companies. Maybe your experience differs, but I've had a sour taste left by such practice.

Colorful language, when applied tactfully, can communicate more completely than plain language. Most aren't very good at using it, though.

There's a small list of companies I'd do a, "Take home test," for. In my experience, most companies that ask for it are looking for free labor.

If the system is so poorly evaluating people that they have to train an irrelevant set of skills to succeed in it, what does that say about the system?

Japan, the golden child of public transportation, serves suburban areas as well as urban cores. I am not convinced it's altogether an issue of population density. It seems more a cultural issue. In America, public transportation is seen as being for people who can't afford a car. In Japan, it's just part of how you get places.

They said they work at MS, not that they work on Teams.

Psychological studies, when ethically conducted, are opt-in. The subject knows they are a part of a study and has a choice not to be and nothing about their lives change if they do. Here, it is not opt in, nobody knows they are being subjected to experimentation, and it has impact on the subjects that they did not agree to sign themselves up to.

Every example you provide allows for much more minute, precise, and invisible manipulation of the affected individual than the meatspace equivalent, for starters.

This is helpful. Thanks for this.

2fa is not magical. It makes an attack require more complexity, but it's not an "and be done with it," solution.

You could easily make an argument that the same philosophy will benefit rapidly growing projects for full time devs. The less "arcane" knowledge needed to work effectively in the code base, the faster new engineers can onboard, the faster old code can have small changes made without breaking something else unexpectedly, and the list goes on.

While your question isn't wrong, how is that fundamentally different from how things were before? How can news be free if it relies upon paying readership for its sustained production?

I guess the issue is that very little discovered internally will ever be publicly disclosed. It feels like a tactic to make themselves look more secure than others when that is not likely the case.

That being said, I think the same behavior is to be expected from any company large enough to need a dedicated security research team.

I think the confusion here is the multiple meanings of, "Should," one being, "morally ought to," and one being, "Is expected to, and raises warning flags that something is amiss if it does not."

Your range for milleneals is much wider than I've heard. The absolute youngest milleneals by the ranges I've heard are around 24-25.

That's a real surprise. I was under the impression that medical equipment was incredibly difficult to get approved for use.

Your analogy assumes that the goal of code is to make your code more and more clever over time, just as a weightlifter seeks to lift heavier and heavier. The goal of code, however, is simply to communicate a process to a computer. Or rather, when that process is subject to change over time, to communicate a process to a computer, simply.

Searching FaBIGWA just sends me to this thread, and I'm struggling to decipher what is in there. Looks like Facebook... And a whole lot of other stuff I can't glean.

Microsoft OneNote was released in 2003, while Evernote was founded in 2007. There were changes Microsoft made to allow OneNote to better compete with Evernote, but they did not make the product itself in response to Evernote.

I've heard, "Product," be replaced with, "Prototype," where a prototype is not a pre-product but more a thing that can be offered that will give information about what needs you should be addressing, how the product might solve them, and help you identify who your most satisfied customers will be (among other things).

While you still have the agility you can only get from zero operational overhead, worry more about finding something people want, who wants it, and why they want it. Scaling is less than worthless if what you're scaling is worthless.

What do you mean by FTA? I'm not familiar with that TLA.

Fair point, but I stand by my statement that it is unhelpful to single out one party. It is the personal and collective responsibility of each person involved.

I don't see how this is a helpful way of looking at it. One engineer objects, and that gets handed to someone else while the manager prepares to fire said engineer. All engineers object, and the team gets disbanded with the project getting handed to someone else. It ultimately falls on all shoulders, especially leadership, and singling out engineers just because they make the commit is, I think, reductive and ignorant of the systemic forces driving people to part take in evil.

My guess is HN users are more likely to have company issued machines with fairly aggressive update policies, making this pain point all the more obvious to them.

If every dish is measured against the most popular dishes and evaluated in terms of how much salt it uses, even dishes not falling into the salt monoculture are being consumed by the salt monoculture.

Playing a video and talking over it is not fair use. Too bad for The Verge, that's not what was done.

Undecorated might be another way of putting it.

I suppose you also think people who leave a lawn gnome outside when they live in a high traffic area are just asking to be vandalized? Opportunity is no excuse for theft.