If I understand the description correctly, microsoft still does this!
https://support.microsoft.com/en-us/windows/privacy/windows-...
483 karma · joined June 19, 2023
If I understand the description correctly, microsoft still does this!
https://support.microsoft.com/en-us/windows/privacy/windows-...
Well. Obviously, yes. But in doing so they still DID scoop out a mathematician in a very unethical way.
In doing so they showed that they basically have a huge gun they can point at X work you care about and develop, and can cut you across the finish line. And take credit for it. Obviously this already _existed_, but is just much more significant because even a rumor can be converted into a complete takeover of a discovery.
> They're not interested, not the kind of entity that can care about theoretical mathematics. These dudes take home 7-8 figure salaries, they solve a Millennium Prize problem then pretty quickly move past it.
I get your point, they don't really care about solving all the maths problems. But they're still going to solve them for clout and profit motives. Up until it stops wow-ing people... at which point they will have likely decimated the frontier of the field.
And this is kind of the root of the entire concern. They will move into the forest and completely steamroll all the problems, then declare victory and move on, leaving only pavement and asphalt behind.
Like git rebase -i as well
Said in perhaps, the most condescending way possible
Im pretty sure said services already exist, making it so your writing doesnt sound or look like AI... but the real problem is surprisingly that we don't even care if the output is AI
Maybe there is value in expending effort and actual creativity.
PMs seem pretty easy to replace. In fact, given any single role to fixate on, it's probably replaceable
I understand why you might for stylistic reasons, but a toggle would be nice!
If you are even thinking about writing clean and testable code, having clearly defined API boundaries, and keeping a repeatable build process, you are probably already significantly above average.
If you are even trying to save, invest diversified, and manage risk as you age... you're probably doing better than like 80% of your peers financially
That's like those stories of LLMs saying "I fixed the vulnerability in your app" by deleting the project entirely
Not to mention the amount of misinformation that can get passed around
Even for a simple system like US social security that has a gradient. For every $2 you make over the limit, you lose $1 in benefits. I've heard countless times misconceptions of people thinking they'd be losing money (as in literally having less money net) by working.
I have to imagine they just asked Claude to dive into a topic and generate example problems along the way.
As for the content... a lot feels like knowledge overload and concepts are introduced without explanation or "why". It basically says "here is a training loop" and never answers my immediate question of "...for what?" It also introduces random concepts like setting the seed that don't look like they're even in the final training loop it provides.
As a comparison, Pytorch itself has docs that go over the entire training loop as well. And it explains why you're loading the data its loading. With examples that run instead of being scattered on.
AI slop is just a more complete reimplementation of the "shovelware" from the 90s
I can agree though that the network effect of "everyone else uses X" is pretty unfortunate and has led to a lot of other issues too, so yes very disappointing
What we've lost is the integrity of this system entirely. No candidate can truly be trusted to implement an age verification system without first getting a check from big tech
I expect Median LoC might be very high with the average developer using AI these days... but the dev who is making atomic changes that are fixing the AI output is probably tiny LoC but way more important
Its also easily possible to have sensitive files misplaced, especially for a general non-technical user that would be the one falling for a browser hijacking attack
So you
1. Reduce morale of Bs with potential. Layoffs or just reducing opportunity affects the whole team 2. Enforce stereotype threat on Bs you've miscategorized, reducing their performance and turning them into Cs.
It probably affects the As too, but I know I'm not there yet, so I can't speak on it.
I get plenty of messages from "recruiters" through LinkedIn. They're not particularly great, but I also only have a few years of experience