deleted by creator

+1. “oh you’ll surely be good if you are early, the train can’t possibly already be overcrowded when it arrives”

I suspect the sales website can’t actually reserve seats itself, but just passes along the request to some other system, which enters “LOL, NO!” in that field for a train that was long-since fully booked.

My guess is that it printed this “null” reservation slip to let you know that the reservation had failed, because otherwise people would think that the printer wasn’t working? It prints the ticket(s), then the reservation(s), then the receipt listing how many things were printed.

deleted by creator

They only issue as many tickets as seats

That’s… optimistic?

https://en.m.wikipedia.org/wiki/Double-entry_bookkeeping f.t.w.

how many thousand do you need to harvest? just saw a video on the process in Kashmir

“Shops over 280 square metres must close on Easter Sunday”

https://www.gov.uk/trading-hours-for-retailers-the-law

TFW “npm install somePackage” adds hundreds of names to your supplier list, some of whom aren’t even adults let alone companies, and the policy says that each new supplier needs to go through a thorough vetting process.

deleted by creator

Seen in a code review (paraphrased):

“Why does this break when you add comments in the middle?”

Similar to how more people have heard of Lockerbie than any other Scottish town of 5000 people.

looking very nice! and in November!

Similar with “get up, Trinity” from The Matrix’s opening scene.

Seems excessive to convert everything to rust when you can use std::shared_ptr and std::weak_ptr to eliminate the memory safety issue?

Your last example reminds me of someone editing Wikipedia to list Ronnie O’Sullivan as the winner of the World Open, about 20 minutes before the final match finished.

They were right, and anyone would agree that it was all-but-certain, but it hadn’t actually happened yet.

This computer.

That was so insane - “we need a unique number, let’s just use the MAC” - it was like people didn’t even think through any of the implications when making ipv6 address schemes.

Similar with the address proposals that ignored the need to minimise the size of core internet routing tables.

Substitute Chaos Bringer to really give everyone flashbacks