It’s because of anti-discrimination laws. In some US states it can be illegal to hire someone for a position without posting it publicly. The concern is that if you’re not posting the job publicly, it can be because you want to prevent certain people from applying.

When you do post it publicly, the company can demonstrate that they allowed anyone to apply, show records that they considered multiple people for the job, and then decided on the internal candidate as the best fit. No room for a discrimination lawsuit.

Source: I’m a hiring manager at a multi-billion dollar company and have actually learned a thing or two from annual compliance training over the years.

Just in case anyone thinks you’re being cheeky… https://prospect.org/justice/police-have-no-duty-to-protect-the-public/

This is the difference between a normal racist and a high functioning racist that knows a failed state can’t effectively oppress the people.

I’ve been doing software development for 20 years and use a GUI (GitKraken) almost exclusively. I know all the commands, but using a GUI makes self-reviewing my code as I commit it a LOT easier. It’s also way less error prone and makes visualizing complex branching/merging operations easier to understand. It’s overkill if you’re working solo or with a very small team though; I regularly work on projects with dozens of active branches.

What changed in their admissions procedures as a result of the court ruling? Is it as simple as just not asking race on the application so they couldn’t hold spots open to fill racial quotas? Or is it more complex than that?

JavaScript and TypeScript are separated? Umm, ok.

Oh, you contributed to the kernel? Name every commit SHA.

The TI-89 was ~$100 when I bought one 20 years ago. Looked it up on Amazon and they’re $100-$150 depending on the specific model. They haven’t kept up with inflation at all, which means they’ve been getting cheaper this whole time…

This is nonsense. Coconuts were spread by humans.

Such an origin indicates that the coconuts were not introduced naturally, such as by sea currents. The researchers concluded that it was brought by early Austronesian sailors to the Americas from at least 2,250 BP, and may be proof of pre-Columbian contact between Austronesian cultures and South American cultures.

https://en.wikipedia.org/wiki/Coconut

Kynseed. It’s like Stardew but pretty different.

!!isAdvantage

I never said that. Sounds like you’re projecting.

Do you also support “just say no to drugs” and abstinence only sex ed? Screens, as a concept, are not literally the devil. It’s unmonitored and unlimited screen time that’s the issue.

E: Damn y’all are dense. “Just say no” was a failed messaging campaign from the war on drugs. The alternative isn’t “say yes to drugs”; it’s actual education about drugs so you know what they are and the actual dangers they can pose. The “just say no” campaign taught that weed was a “gateway drug” and that everyone that tries the devil’s lettuce will start using cocaine, amphetamines, and there’s a 100% chance you’ll become a homeless junkie and die of an overdose. It was about as ignorant as you can get.

Give me heavily subsidized US made electric vehicles or STFU.

Hopefully it’s a 96 minute reenactment ofRocket Man.

Not clones, more of a ship of Theseus scenario. A fungal network can be “one thing” because we see it as a single interconnected system. But parts grow and die over time. It doesn’t have individual cells that are infinitely old, but the one wholistic fungal organism, as we define it, can live forever through regrowth. There are types of jellyfish that can also “live forever” in this same way.

I was against the change when I read this post, but now I have to say I love the ice blue color on the AMOLED black background. Nice.

I usually go by “fuck you”. Like someone yells out of their cube “who’s goddamn code is this?!?! Ah, fuck you”

Also codemancer

The point would be a lot more impactful if they didn’t make up a story to support their position.

We solve that problem using naming conventions. Branch names must start with the issue key (we use Jira). You don’t do anything in that branch that’s not part of that issue. If you do, you must prefix the commit message with the issue key that it goes with. The commit itself identifies what changed. The Jira issue provides all the backstory and links to any supporting materials (design docs, support tickets, etc). I have to do a lot of git archeology in my role, and this scheme regularly allows me to figure out why a code change was made years ago without ever talking to anyone.