Apologies for the tangent:
I know we’re just having fun, but in the future consider adding the word “some” to statements about groups. It’s just one word, but it adds a lot of nuance and doesn’t make the joke less funny.
That 90’s brand of humor of “X group does Y” has led many in my generation to think in absolutes and to get polarized as a result. I’d really appreciate your help to work against that for future generations.
Totally optional. Thank you
We should always add a mental asterisk to the names of male researchers who discovered things while women were oppressed.
That said, this meme is playing loose and fast with the specifics, which undermines that important message.
Just picking the first one:
Payne’s work was her Ph.D. thesis and Russell did not tell her not to publish it, her advisor did. The advisor told her not to rock the boat in her thesis. This is good advice that even Einstein was given. Payne, badass, declined.
When Russell later reproduced her research, he cited her thesis as the “most important research” he’d seen on the subject.
The real snub with Payne is that her title was “Technical Advisor” for 20 years despite being well regarded as a full time professor. It wasn’t until the 50’s she was recognized as a professor, when she was also made chair of the department.
Source: https://www.amnh.org/learn-teach/curriculum-collections/cosmic-horizons-book/cecilia-payne-profile
Too long, didn’t read
I see your concern, but in practice that’s not what happens in languages like Java and Python with exceptions. Not checking for exceptions is a choice because everyone knows you need to check in your top-level functions. Forgetting to catch is a problem that only hits newbies.
Oof, some of these comments. Sorry on behalf of the edge lords, OP.
But the entire point of Rust and Result is… to force you to make a choice of what should happen
Checked exceptions also force you to handle it and take way less boilerplate.
Zigbee or really any Bluetooth alternative.
Bluetooth is a poorly engineered protocol. It jumps around the spectrum while transmitting, which makes it difficult and power intensive for bluetooth receivers to track.
The government had a warrant, read the article.
It’s just made confusing by the fact that the thief had signed into the victim’s phone, so it makes for a good clickbait story “police got the wrong guy’s data”
If by “when asked” you mean “given a search warrant with very clear evidence that this man had stolen a car”, then… Yes? I’m not sure what you’re trying to prove here.
The ex-boyfriend had signed into the guy’s phone. It’s not like the police just cast a wide net and randomly got his data.
Look I never said I disagree. My point to OP is just please don’t make up shit that straight up isn’t true. Pick a real issue, not some made up paranoia.
Re 1: People keep lumping Google with Amazon and Meta, but Google does not sell your private data and alerts you if it finds out the government to accessed your data. People keep assuming that because the general tech community sells data that Google does it too, but check their privacy policy or just ask anyone who’s worked there. They don’t.
User data at Google is locked up tighter than fort knox. That’s why the Snowden leak was such a huge deal, because the NSA was taking advantage of a security flaw that Google didn’t know it had to scrape user data. Google patched it immediately after they found out.
Amazon, Meta, and Uber, are much less scrupulous.
Because security through obscurity is not security at all.
I’ve been a big fan of monorepos because it leads to more consistent style and coding across the whole company. It makes the code more transparent so you can see what’s going on with the rest of the company, too, which helps reduce code islands and duplicated work. It enables me to build everything from source, which helps catch bugs that would only show up in prod due to version drift. It also means that I can do massive refactorings across the company without breaking anything.
That said, tooling is slowly improving for decentralized repos, so some of these may be doable on git now/soon.
Yes. The problem with cookies was that they could be used to track and identify you. If this can’t do that, then what’s the issue?
They just added a fee so that AWS can’t copy it without paying. What’s the big deal.
To say it’s “completely incorrect” is an exaggeration at best. The paper you cited is far more nuanced than that.