299 karma · joined July 8, 2011
There's physiological differences in the brain though
https://en.wikipedia.org/wiki/Attention_deficit_hyperactivit...
Right, because there's literally no alternative to fortune-telling magic but more kinds of fortune-telling magic. If there were already a conceptually different prediction service with useful and measurable accuracy, the tarot card place would need to have superior accuracy or some other hook, otherwise they'd go out of business. Ultimately the differences would be measurable and demonstrable.
Marketing team could be selling snake oil, I get it, but snake oil only exists where a real, functioning product doesn't, otherwise there'd be results to compare.
Multiple political campaigns over the past several years clearly thought Cambridge Analytica's data/services were more valuable, or uniquely valuable, compared to services like Facebook or Google. If Google or Facebook were equally suited to the same purposes, I imagine they would have simply used Google or Facebook.
Huh, the article doesn't even mention Trump
>every candidate does the exact same thing
But the issue isn't that ads are being targeted. The article specifically cites data misuse. The same is true in the case of CA, they were not supposed to be selling people's data to third parties.
Real wages have increased +1.5% March 2018 - March 2019, which the article would do well to point out. Citing that growth has topped 3% for nine months is almost in some ways misleading if it turns out that growth doesn't confer a similar increase in purchasing power.
The BLS tracks real wages which is where I got my 1.5% figure. To further put things in perspective, from March 2018 through March 2019 average paychecks increased by about $30 a week. At the same time, real average weekly earnings only increased by about $5.
I don't get why they would avoid (edit: less so "avoid" more like "miss/omit") this subject completely.
Semantically it's not a question of "who can use their product" it's a question of in what fashion are users permitted to use their product, what behaviors are/n't allowed on that platform. Facebook didn't institute or enforce a "no Louis Farrakhans" policy. They set boundaries on what kind of behavior is or isn't acceptable for continued membership and participation on their platform, e.g. no anti-semitism.
Even a free-speech shithole like 4chan has a distinct moderation policy for each individual board. There have to be rules for a social/discussion platform to serve an intended purpose, otherwise the platform becomes repurposed by its users or ceases to have any purpose to anyone. If Facebook can't dictate its policies they can't dictate what shape the platform takes.
But the fact that it has dictated its own form is why it's Facebook. That is to say, perhaps Facebook couldn't be the platform on which people wanted to post anti-semitic content, if it didn't actively purge such content from its platform. If Facebook can't dictate what kinds of content are healthy for their platform then there could very well not be a Facebook at all.
You mean, like, releasing some leaks, but not releasing other leaks? Yeah, that would really suck.
That is to say, in practical terms, consciously choosing to not believe in something is the same as not having any concept of that thing to begin with.
It actually is. Most people are asymptomatic, or their symptoms are so mild that they confuse them for a pimple.
One of the things I've been paying attention to as I get older is how many unique experiences a thing offers. Games that are hundreds of hours long, or otherwise provide hundreds of hours of entertainment, generally involve a lot of repetition. Repetition is intrinsically unmemorable.
The games keep you busy, and you might not describe yourself as bored while playing them, but it's not like you can remember all of the riveting times you fought a Zubat. And in that sense, was it an optimal use of time? Sometime I find it disturbing to think about. There are games where my total playtime adds up to literal months, but the number of unique memories I have of actually playing are depressingly few.
Did you get everything off of your chest yet? Did you or your alternate account have any other grievances that you wanted list?
Trump supporters were assaulted, that much is factual. The notion that they were a) liberal b) activists, is not a notion you can support with facts.
>Real average hourly earnings increased 0.7 percent, seasonally adjusted, from October 2017 to October 2018.
Tests only really catch bugs when you're refactoring the implementation of something while trying to keep its behavior the same. You're right, in many ways, tests exist to be broken. But they still serve their purpose. They either break because you unintentionally changed behavior and need to fix your code, or because you intentionally changed behavior and need to change your tests.
But why delay the shipment of features/fixes to the customer for any of these reasons?
If code quality and human understanding is the actual rationale, it could make more sense to review code after it has shipped. In that way, it would cease to be a bottleneck for the developers or customers. Additionally, any bugs that appear in production could be accounted for during the refactoring process.
Saying that there is value to a practice is the easy part. We're forgetting to ask when to code review and whether or not code review should ever be a blocker to other processes.
Proper test coverage and human QA to me is the most effective approach to not shipping bugs, because it really doesn't matter to the customer what the code does or doesn't look like if it runs. And I just don't believe that code review is an efficient means to catch that if user is in a state of X and tries to do Y to Z that the app blows up. That becomes most apparent when that code is running in the full context of the application, not when viewed as a git diff. A bug is so often a perfect storm of seemingly innocuous but conflicting/insufficient behavior than it is some block of code that is clearly broken at a glance.
There is something to be said about stylistic and architectural issues and code reviews do give an opportunity for asking questions and driving "better" code. But this is actually just another reason why I don't like code review. "Better" is subjective and there's always another level of "better" to be reached. If I held them to my own personal standards sometimes I'd be asking for a rewrite. So what do I do, suggest that they improve their code, but not to the full extent that I feel it could be improved?
I hate code review.
This was high school for me. I would have weeks to finish a significant paper. I would inadvertently wait until the night before, stay up all night working on it, and generally I would get a good grade, often an A. It was like the time and effort I would have spent on it was concentrated into a single 12-hour rush where the deadline pressure squeezed my best efforts out of me.
At no point did I think "I should work on this paper, but, nah". In my head I was always getting around to it, but never did. Same was true for homework. I would be trying to finish first period's assignment on the school bus, next period's assignment in homeroom, another assignment in study hall, another assignment at lunch, etc. A lot of copying people's work.
Also I have crippling ADHD and can barely hold a job.