Once upon a time, I accidentally created a folder named “~” in my home folder (the company provided scripting framework would inconsistently expand variables, so the folder had a ton of stuff inside it).

I ran “rm -rf ~” and only panicked when I started to wonder why it wasn’t taking too long.

Good news is that it only managed to get halfway through my local checkout of aosp before I stopped it. Bad news was that it nuked most of my dotfiles.

The original article smelled wrong when they claimed to have broken AES. Thankfully, Bruce Schneier is far more authoritative than I ever will be and gives a short and succinct list of links to debunkings of this.

None built in from what I recall. That was from back in 2011, so it’s possible things changed since.

Reading through, it looks like retries do exist, but remember that duplicate packets are treated as a window reset, so it’s possible that transmission succeeded but the ack was lost.

I remember the project demos from the course though - one team implemented some form of fast retry on two laptops and had one guy walk out and away. With regular wifi he didn’t even make it to the end of the hall before the video dropped out. With their custom stack he made it out of the building before it went.

I’ll need to dig through to find the name of what they did.

To be fair, because of window size management it only takes 1% packet loss to cause a catastrophic drop in speed.

Packet loss in TCP is only ever handled as a signal of extreme network congestion. It was never intended to go over a lossy link like wifi.

Only on signup

Anything using Blind as a “verified industry source” is going to be skewed to the type of person who uses Blind. Beyond that, it’s low sample size, and there are suspiciously round fractions for some of the larger companies. Worse, because Blind is blind - this doesn’t represent current employees, but merely people who worked at some point in the past at those companies.

Not saying it’s not good - just saying not to get overly excited over a badly done survey

Seriously though - JIRA isn’t always a massive pain in the ass. It’s just the way it’s used that sucks. Workflow restrictions so devs can’t move tickets from testing back to in progress, dozens of mandatory fields, etc.

When your tools start dictating your workflow rather than the other way around then it’s time to switch tools.

Friends don’t let friends use JIRA

I have either written or gotten a variant of every single one of these comments 🫠:

Please include the JIRA task in the commit title.

Did you run any manual testing?

Where’s the PRD link in the commit message?

Can you please split this into multiple smaller commits?

Can you combine these two commits?

Did you email Jon about this because he’s working on that project with Sarah and you might be duplicating efforts.

This should be named BarFoo instead of FooBar.

Why aren’t you using CorporateInternalLib16 that does 90% of this?

Why aren’t you using ThirdPartyPaidLibByExEmployee?

Why aren’t you using StandardLib thing you forgot existed?

All our I/O should be async.

All our hot loop code needs to be sync.

This will increase latency of NonCoreBusinessFlow by 0.01%. can you shave some time off so we can push in feature B also?

Please add a feature flag so we can do gradual rollout.

What operational levers does this have?

Lgtm - just address those comments

Holy propaganda batman!

The list of articles on that website is…extremely focused on one subject only.

Locks are only held during system calls. Process termination is handled on the system call boundary.

You’re projecting windows kernel insanity where it doesn’t belong.

What the duck Microsoft bullshit is this?

There is no concept of locked files in extfs, much less inside the kernel. Resource locks and unkillable processes is some windows bullshit that no sane operating system would touch with a ten foot pole.

Where does the 93 come from? The percentage is almost correct, but it should be 11 (1.074%)

Nope. Bitkeeper used it in the master-slave pairing and the term was carried forward. Gitlab did a whole writeup about it.

Got it. From this list: http://bbslist.textfiles.com/408/oldschool.html

408-336-3134 Ben Lomond, CA Pyrzqxgl (1986-1987) Tané Tachyon Pyrzqxgl tree-structured discussion BBS software

I can see why you called it pretzel

Plover-net perhaps?

Do you remember the area code?

$previous_job allowed us to pick. One of my coworkers had to replace his laptop, and I convinced him to try out Linux this time. I handed him the bootstrap script and he was back to working by the afternoon.

Our CEO got wind of this and said as a matter of policy everyone is switching to Linux unless they have a good reason (needing excel for financial reports is a good reason). The two new hires who had been setting up their dev environment for over a week at that point were the trigger for this.

Intel, whose investment will be over five years, will pay a corporate tax rate of 7.5% instead of 5% previously. The normal tax rate is 23%, but under Israel’s law to encourage investment in development areas, companies receive large benefits.

Usually these types of grants are never a good investment but the increased corporate tax rate alone covers a third of the grant (9b yearly taxable revenue at 2.5% over 5 years comes out to 1.125b).

I was not expecting the drama around it. Is the issue truly a different orthography or is more like a different font/ligature issue?

EDIT: forgot the article I found on it: https://restofworld.org/2021/tulu-unicode-script/

Removed by mod