1,294 karma · joined October 13, 2020
If this sort of malice isn't enough to bring accountability to those responsible, do we even have rights?
I feel like we need a separate organization with one job: to investigate, arrest, and try corrupt government officials. Take the good ol' boys club out of the equation.
Still working on how to get her to stop obsessing over stupid crap.
As requested, the quote:
> Companies tend not to have data on the sexual orientation of their employees. Such studies are not possible to do.
The studies are absolutely possible to do. Throwing up our hands because companies "tend not to have data on sexual orientation" reads like a cop-out when the comment you responded to was attempting to get at some data around this very issue.
> The McKinsey stuff and other stuff is generally publically available data.
Is it? I found a report [1], which isn't the one which I previously remember seeing but it'll have to do since that older one evades me now.
Look at the footnotes. Several pages say their source is the "McKinsey Diversity Database". I searched for it on Google and DuckDuckGo and it didn't show up for me. Do you have a link to the underlying data for this database? I tried and failed to find one.
Lastly, review the authors at the end of the doc. If you put the authors' bios at the top of the report, the conclusion would be surprising to exactly zero people. That doesn't mean their conclusion is invalid, but given that much of their data is tied up in a "diversity database" that I can't find is VERY suspect.
[1]: https://www.mckinsey.com/~/media/mckinsey/business%20functio...
These diversity "studies", as the grandparent points out, are light on data and heavy on marketing. Several years back when I looked up the McKinsey 2012 (or 2013, whichever) study that started all this, it was a marketing flyer with zero data.
It's really convenient you can make such a hefty claim and provide essentially no evidence to back it up.
There are many languages better suited to delivering native apps. The pitfalls of electron are already well understood. If you need electron ANYWAY, then you might as well just use electron.
What is the difference (to a layperson) between cherry-picking participants and rejecting participants because they do not meet your study's criteria?
Who funds this agency?
Do the members of the reviewing agency have their own biases, and might those biases tarnish the reputation of a study that is actually well-conducted? (hint: this already happens in journals)
Be on the lookout for malaria appraisals on coming episodes of the Antiques Roadshow!
edit: wow, jokes are not well-received I guess
You are operating under the assumption that foo() changes in a vacuum. That is an invalid assumption for lots of software changes.
Commits are supposed to contain one logical change each. That logical change may or may not cross function boundaries (often it will).
Reverting a commit should revert the logical change. That is how you accomplish what you're after in git.
If your repo ends up in a weird state, learn how to fix it. It should not be terribly complicated, especially if there is no rebasing happening.
Taking GPL'd code and redistributing it without making the source available IS stealing. It is community code. If you want to use it, you have to give back. Otherwise pick something with a BSD or MIT license.
This improvement for me has been really recent. Maybe it helps you too. Good luck!
I am not morbidly obese. I have a pretty small frame and am about 5 ft 6 in tall. My BMI before cutting my portion sizes down was on the upper end of the normal weight range (24.9).
I tend to be a fast eater, and I think that did me no favors.
It makes a lot of sense in retrospect. But when you're not obese, cutting your portion sizes is not the first thing that comes to mind as a method for improving health.
Is it as good as a separate dongle or push notification? No, it isn't in terms of device verification. But it is more convenient. Unlike a password, TOTP secrets never have a reason to leave your vault once you have stored them. One thing I dislike about push notifications is the possibility for fatigue attacks. Even if you only get one from an attacker, a fat-finger could provide access to your account. Oops!
If you are using a vault properly, even leaking the master password is not enough for an attacker to break in. They also need a copy of the vault. Or they'd need to have compromised a device on which you actively use the password safe (but that's tough to defend against).
To me, TOTP seems like a good middle ground. It isn't vendor locked. Unlike biometrics, TOTP secrets can be changed. TOTP gives users the power to choose how secrets are stored and how one-time-passwords are presented.
Check out https://oese.ed.gov/ppe/.
I live near a school district that is well-known for high quality education. The urban district nearby has 20% higher per-pupil spending and the quality of education is MUCH lower.
A BDFL is great if the dictator is competent. A committee is also great if the committee is competent (overall).
Most people don't have what it takes to be a BDFL. But a few do. And for those people, the answer is to take good notes and get the hell out of their way.
If you reduced the maximum sentence for murder to one day in prison, there would absolutely be a lot more murdering going on even if everything else stayed the same.
It's very common for natural gas to be used to heat homes and office spaces, at least in the US.
Additionally, water heaters and dryers might use natural gas. Gas stoves do, too.
You ever notice how CO alarm instructions have a blurb about not putting the alarm too close to your furnace, or too close to a gas stove?
They will intentionally NOT alarm if there is a low, persistent level of CO that probably has devastating health effects over the long term (think 20ppm in your house all the time).
Some years ago, my furnace had a cracked heat exchanger and, unknown to me, was pushing CO into my living space. I only noticed by luck. I walked by one of my CO alarms, hit the "max level" button and thought to myself that 25ppm is quite high. So I reset it and checked it again the next day. Sure enough, it shot back up.
CO2 is much easier for our bodies to deal with than CO. CO2 won't kill you unless it's at exceptionally high concentrations. In cold regions, gas burning furnaces produce a good deal of CO.
There are alarms for CO, of course. But in the course of researching CO & UL standards around alerting, I found that most consumer CO alarms don't even alert until CO is above 30ppm. Additionally, for UL-certified CO alarms with an ambient "max reading" function, they don't even report anything below 10ppm.
Levels as low as 5.5ppm have been shown to significantly increase risk for low birth weight: https://pubmed.ncbi.nlm.nih.gov/9872713/
For context, the CO level outside, where there is fresh air, is 0-2ppm.
Carbon monoxide really is the silent killer and doesn't get talked about enough.
Tossing a five gallon jug on your shoulder and running up and down a flight of stairs for hours is REALLY hard work. And yet you don't see people take this on as a job and then complain about it.
So instead someone goes out and gets an entry-level position. The options are limited, because they have no skills. The problem now is they never invest in building skills, so they are stuck in shit-tier jobs forever.
I want to have some empathy for this. But if I go to a convenience store and somehow it takes the cashier 10 minutes to checkout 3 people, that empathy becomes hard to find.
At the end of the day, every person getting a paycheck needs to produce more value to the business than they get paid. The only other way is to tax people who DO actually contribute and spread the money around. There are some serious concerns of fairness about that.
For one, building out anything of complexity in Terraform often involves some trial and error to make sure all the resources are wired together correctly.
For two, there are some Terraform changes that can incur downtime if you just let Terraform destroy and create resources. The solution I employ for this is what I not-so-affectionately call "Terraform surgery". It usually entails standing up the new resource(s), cutting over to them, and then destroying the old ones. Sometimes I will manually remove some stuff from the state file and delete it once Terraform has performed the cutover.
That stuff is possible to do in CI, but it would be inefficient and painful.
To me, the biggest benefit of Terraform is managing changes to cloud resources. You know what resources are added when, why, and by whom. You have a mechanism for promoting changes between environments confidently. And if your infra ever blew up, you would be able to put stuff back.