You know how all employers have talent pools? Think of those applicants as being in a barrel and you can scoop out a prospective applicant pretty easily. Regular companies do this no problem.

Now Deloitte, being more profit focused company looks at that and says “There’s obviously a better and cheaper way to do this, we’re Deloitte, we know how to save cost and deliver”

They have discovered that if you go all the way to the bottom of the barrel, almost no one can extract the useless hard fibrous bottom. Deloitte broke the mold here, they exclusively extract the bottom, each applicant making the talent pool slightly larger for regular companies. Chewing the fibers into a grotesque cud-like mass that is impervious to all possible methods of digestion known to corporate kind.

They have learned to extract and refine so much of the bottom that in 2021 they ran out! They hit the very floor the barrel was placed on. Deloitte not to out do themselves thought “Hey, we did so well with the whole useless bottom thing, our clients literally can’t get away. What if we tried to extract the literal floor itself? There’s no end to it, we can extract it endlessly, forever!”

This method of extraction, gave Deloitte an ace in the hole, there’s no possible way for another corporation to acquire talent in this manner! The quality of candidate here can’t be overstated, they literally are chunks of the literal bedrock of society that produce work that would make a Jr vibe coder’s AI segfault just by parsing it.

Deloitte has evolved into a parasite that sucks the life force from their clients and provides products that endlessly lose them money. Their crown jewel is literally having the worse possible employees that could provide a “working” implementation of what was requested by their client.

Source:

I’ve literally had to clean up Deloitte’s messes when their clients don’t understand why the provided software doesn’t work. I’ve seen literal grade schoolers who can write more competent applications.

I’ll give you that. He’s an advanced level of stupid that I’m surprised he has any amount of influence at all…

I don’t think there’s ever been smart ones… They constantly have to scapegoat someone lest the rabble finds out they’re just pilfering the country and everything is collapsing.

Yes.

Yes and no, its an official release, but basically these are “We think this issue is resolved or this new feature is ready”. The GrapheneOS team does a gradual rollout to prevent causing people issues (since people literally can live out of their phones).

Alpha channel users get it, if they don’t notice any issues roll it out to beta channel users, if no issues found in the wider beta users, roll out to stable.

Basically it prevents a bug from being pushed out to everyone and causing headaches for the devs. You can’t know everyone’s use case so by having a smaller number of users who are expecting breakage you can find bugs or showstoppers early before it lands on a more nontechnical users device.

Are you on the stable branch? Graphene does roll outs slowly (alpha->beta->stable), once the changes have been proven stable they get pushed out to everyone. Judging by the fact the devs have been pushing releases, the changes aren’t stable enough for prime time. It happens.

If they could read, they’d be very upset.

There’s definitely at least one thought marble rolling around in there. His “no thoughts, just vibes” requires his tongue out.

Chase is life, but who was really chasing who

Runescape Private Server

William Murderface

/s

Why did I read each of those in my head differently?

I hate how this is always on fucking point. These people don’t have empathy until it affects them in a personal way, then all of a sudden it’s “who let this happen?!”

It was you, you fucking dipshits, by not having the emotional intelligence to be able to think for one second in another person’s shoes or think out the end conclusion to a piece of rhetoric.

Inside git’s internal plumbing folder, git holds a file with the branch name and all of the references (files and changes) for that branch.

When you make a new branch git will update its internal plumbing checking to see if the new branch already exists, updates its references to the new branch if it doesn’t (all held internally in a case sensitive way). It will then make that new branch file, git has already checked that the case senitive name for the branch doesn’t exist internally, so it should be good to go.

Part of its process is creating that internal branch file… But wait!

Windows doesn’t have case sensitive naming so when it tries to make that new branch file it will overwrite the old one (since it shouldn’t exist by git’s own reference!) All of the files and references for it now get nuked.

Now you’re at best back to wherever that originally named branch came from, at worse your .git folder is properly borked.

Way ahead of you… I have a Brocade ICX6650 waiting to be racked up once I’m not limited to just the single 15A circuit my rack runs off of currently 😅

Hopefully 40G interconnect between it and the main switch everything using now will be enough for the storage nodes and the storage network/VLAN.

Home Petabyte Project here I come (in like 3-5 years 😅)

But…! But…! It could teach children the different types of poker hands! Plus you have to win a certain number of chips in order to progress! This is clearly a type of gambling and should require the utmost care to prevent a child from becoming a gambling addict!!

/s (god I hope that’s not needed)

By the way that’s the actual reasoning why they gave it the 18+ rating.

It’s not, that’s the problem.