oleggromov

Oh wow, my apology - didn't know that and didn't notice the length of the hexademical number. TIL.

There's a typo with 'ULL' string suffixes in the hexadecimal numbers in the first code example.

Good project, nice write-up.

However, to me as a person with an anti-library as well, this kind of defies the purpose of having it in the first place. I can't say I browse my books too often but when I want to find something, I'd rather browse physical things on a shelf rather than some out-of-date UI with fetched thumbnails. Of course the organization happens in physical space too: this is why we have shelves, labels and such.

Obviously no judgement or criticism for the author, just sharing thoughts.

Me too. It's phenomenal, especially the first book and the pilgrims' stories. Such a moving mix of religious mystics, science fiction and the dreaded AI. The second one builds up the tension and the last 2... are good.

Or, even more likely, a bad solution for a non-existent problem.

It's such an irony that for such a topic, website content is actually overflowing on a mobile safari and gets out of the container so the website appears broken.

I came to comment that at least something good happened to the otherwise cursed project... but you made me reconsider.

> Antibiotic resistance is a problem for society. Infection is a problem for the individual.

Unfortunately not necessarily. For many chronic conditions an individual may very well develop an antibiotic resistant bug. There's even plenty on YouTube about standard penicillins and strep bacteria that start growing right inside the antibiotics. Look it up, it's fascinating.

It seems to me that since airlines can't force you on a plane except for taking your luggage hostage, you're free to drop as long of a 'tail' as you wish. I'm wondering whether they'd put you on a black list or something for doing this consistently.

Sorry to hear that. Sounds like not a lot of fun!

Of course I can understand it from their point of view. But this doesn't make it any more sensible to me as a consumer of their services.

In the aforementioned situation I wasn't trying to exploit the airline, it was a simple mistake that happened and could be easily alleviated. But the rigid processes, precisely the ones where accountability sinks, made it impossible for the humans involved to correct the mistake.

I still stand by the ridiculousness of that. If not the logistics quirks per se, then the fact that this completely unrelated matter dictated the resolution of the situation against common sense and my interest.

What makes this even worse is that presumably the PR department of that very company had to be involved later and they still spent their employees' time and money to compensate me for the mistake that could be corrected for free.

> It's generally to protect revenue because buying A-B-C instead of B-C can be cheaper, and hoards of people used to just segments to save money. So they just assume everyone is trying to cheat them.

Isn't it ridiculous in the first place that flying A-B-C is less expensive than B-C? These are the pricing games airlines deliberately play to make more money out of nothing.

Leaving aside the no-show rule, which doesn't make much sense to me, this situation is a good example of an accountability sink.

The intermediary I booked the tickets with made an obvious mistake and showed the wrong airport code. Maybe the airport opening was meant to happen earlier, and the intermediary had already updated their emails or something like that. They refused to do anything meaningful and did not even acknowledge their mistake.

The fact that I was compensated by the airline that had nothing to do with this mistake is even more astonishing to me, although they were obviously protecting their brand reputation.

I once booked a plane ticket from my home town airport to another country. The purchase notification said something like "PVA" instead of "POV". I looked it up and turned out, the newly built airport that had this exact code was about to open. In a week or so, so I assumed that I'm indeed flying from the new one and forgot about it. The purchase was made through a booking aggregator similar to Expedia.

On the day of travel I took a taxi to the new airport, which is 40 km outside the city. The taxi driver couldn't care less about where I was going. Upon arrival, there was much fewer people than I expected but I shrugged it off. At the entrance though I was asked where I was going and if I was an employee. Apparently the new airport was still closed and my fight was from the old, still functioning one. The one with the code not shown in the ticket purchase receipts.

Panicking since it was only about an hour until departure, I took a taxi back to the old airport, which was a desperate 40-50 minute drive to only realize the plane had already left.

I was flying abroad, with a connection the next morning, about 10 hours later. So I thought that the problem could be solved by just arriving there by any other flight, which I booked almost immediately. However, the airline representative (yes, there was a human to speak to that I could reach easily by phone) told me that a no-show for any segment of the flight invalidates all subsequent ones. There was no way I could convince her that it wasn't my fault. Perhaps there was a rigid process in place that disallowed her from helping, even though I'd make it to the second flight on time.

I ended up buying 2 new tickets, of course more expensive and less convenient ones. This taught me an important and rather expensive lesson on why connected flights with a single airline are sometimes the worst.

Funnily enough, I was bitten by this rule one more time when I didn't show to a flight in to the country due to visa issues (it was covid time) and wasn't allowed on the flight out of it because I didn't show up to the 1st flight, the flights being 1 week apart - but booked in one go.

As to the previous situation, I managed to get compensated by the airline (not even the intermediary!) about a year later after posting a huge rant on Facebook and getting their attention to the situation.

This is wonderful. Thank you.

Working on an interactive SQL tutorial for intermediate+ SQL developers, introducing you to and showing the power of such concepts as JOINs, pivoting (flipping rows to columns & vice versa), subqueries and common table expressions, including recursion, UNIONs, row locks, and some other small things.

The thing will be browser-based and, hopefully, both entertatining and educational.

This is a great inspiring story and wonderful books. Thank you! Trying to find them now.