One upvote is not enough.

I once wrote a commit message the length of a full blog post comparing 10 different alternatives for micro optimization, with benchmarks and more. The diff itself was ten lines. Shaved around 4% off the hot path (based on a sampling profiler that ran over the weekend).

Ew no.

Abusing language features like this (boolean expression short circuit) just makes it harder for other people to come and maintain your code.

The function does have opportunity for improvement by checking one thing at a time. This flattens the ifs and changes them into proper sentry clauses. It also opens the door to encapsulating their logic and refactoring this function into a proper validator that can return all the reasons a user is invalid.

Good code is not “elegant” code. It’s code that is simple and unsurprising and can be easily understood by a hungover fresh graduate new hire.

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.

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

If you’re aware of someone or a company violating sanctions, you can earn up to 20% of the fines as a whistleblower.

Considering the fines start from 100,000 per transaction, you could easily retire on a single report.

No need to wait. Here’s their statement: https://www.anera.org/press/anera-convoy-attacked-en-route-to-emirati-red-crescent-hospital-four-killed/

No Anera staff were harmed, though one Anera employee, who was in the second vehicle, witnessed the incident at close range.

Despite this attack, the remainder of the convoy continued its mission and successfully delivered the critical aid to the hospital. Anera has coordinated with the United Arab Emirates 24 prior shipments for the Emirati Red Crescent Hospital since May.

Considering that Hamas are holding bodies and hostages and demanding an end to the war in exchange for releasing the hostages, changes to that situation are quite relevant.

Are you communist left? Or socialist left? Or cryptoanarchist left?

Are you republican right? Or fascist right? Or tankie right? Or cryptocapitalist right?

If it’s off by one (center left instead of center, mixed instead of high) then just chill. It’s close enough. The point is to highlight the extremes, especially for when someone went headline shopping and posted some relatively unknown source.

I needed a laugh. Thank you.

Deif is dead. Haniyeh is dead. Something like 40% of all the senior leadership is dead.

The hostages aren’t keeping them alive, they’re putting them in the crosshairs.

Do you have a copy of the bridging proposal? I haven’t seen any actual text.

I have to say that this is the most color I’ve seen in months on the actual reasons why. On first read, it gives an understanding that both sides are willing to approach a deal - but lack trust in the process and the mediators ability to coerce the other side to actually commit and follow through.

A more cynical read (my second one) through this is that Hamas is still viewing civilian hostages as an asset and leverage. They are hesitant to get a six week ceasefire because they think they should get more than that for civilian hostages. Recent reports are making it clear that Hamas is executing the hostages. Whether as part of their negotiations, a breakdown in discipline, or just simple evil - the mediators have failed to impress upon Hamas the depth of their strategic mistake.

I wonder if this was some concession by Hamas as part of the negotiations

You got me. I was trying to bait you into saying that ethnic cleansing is obviously a bad thing and we should apply a consistent standard to avoid dehumanizing rhetoric.

So perhaps they can allow Israel to exist within US

It sounds like you’re suggesting ethnically cleansing Jews from the region. How is that any better than suggesting that all Palestinians be moved to Qatar or Iran?

There’s a fine line between disrespecting a fallible opinion and disrespecting the person. In writing, it’s easy to cross that line. It’s ok to disagree with people, but it’s important to sometimes take the step back and remember that the person is larger than any singular decision. There’s likely context you’re missing that lead them to that decision.

The biggest thing to remember is that more likely than not, if you really and truly fuck up your job, chances are the worst you do is create extra work for your team. They probably won’t even be in danger of losing their jobs if you truly screw up. It’s not likely that people will die. The blast radius of most software engineering jobs is incredibly small.

Good luck with it!

It is “fun”, and there are lessons that Ruby has that should be taken elsewhere, like the principle of least surprise. The most important one is MINASWAN: Matz is nice and so we are nice.

Matz described Ruby as Lisp with C semantics, and Perl convenience.

There’s a reason the CLI flags can put it in “perl mode”