Metropolitan Opera’s Le Nozze di Figaro: A Mixed Experience | May 03 2025, 04:14

I’m not even sure whether to praise the Metropolitan Opera or criticize them. They have a new production of Le Nozze di Figaro, and this year they are showing it exactly once in a live broadcast on April 26 and exactly once in a recording on April 30, and only in select theaters worldwide. They offer recordings for a fee, but never from the current season—well, for obvious reasons. So, Figaro will only be added to their library next year.

Our local cinema failed the live broadcast—they apologized, sent us home, and promised a refund. Four days later, a recorded session was shown in the same theater. That went almost smoothly, if you ignore the severe sound issues during the first 30 minutes. Since I can’t tell if both were issues with the specific theater or poor organization by the Met, I dropped them a support line just in case.

And support apologized on behalf of the theater and, as a nice bonus, sent me a link to a video 1280 × 720, 3h37m, asking me to watch it by Monday because after that the carriage turns back into a pumpkin. Well, okay, not quite an mp3 file, but it streams via m3u8, and yt-dlp manages to convert it into a 6-gigabyte mp4 file in 3 minutes.

Interestingly, this recording starts with the opera artists singing the Ukrainian anthem on stage before the curtain is even raised. This introduction was not shown at the cinema.

I am honest, and of course, I won’t give the file to anyone. I will watch it myself when convenient, and then I may delete it, or might keep it on my personal laptop for personal use. And I might even buy a subscription to the Met this weekend. In short, they’ve done well, though, there is a small nuance 🙂

Hidden Flaws and Covert Repairs: The Citicorp Skyscraper Crisis | April 29 2025, 21:40

Check out this cool story on the Veritasium channel about a critical flaw discovered in the Citicorp skyscraper after the building was finished.

The incident occurred 46 years ago, in 1978, just a year after its inauguration, when structural engineer Bill LeMessur discovered a critical error in the design of one of New York’s most ambitious skyscrapers — Citicorp. The 59-story building was constructed on stilts that were positioned at the center of each side rather than at the corners, as is typical, to preserve an old church that stood at one corner. This unusual decision required a unique system of diagonal braces (chevrons) that redistributed the loads. However, it was later revealed that due to the substitution of welded joints with bolted ones, under diagonal wind — initially not accounted for in the calculations — the building could completely collapse from a hurricane with just 110 km/h winds, creating a real threat to the city with a shocking probability of 1/16. Had it fallen, the surrounding skyscrapers would have toppled like a house of cards.

Recognizing the scale of the threat, LeMessur clandestinely began overnight repair operations named Project Serene, literally sealing every vulnerable joint in the structure with metal ‘patches’ while office workers went about their day undisturbed. Neither the employees nor the citizens were aware of the danger in order to avoid panic. A covert evacuation plan for ten city blocks was even developed. Despite the patches, everything depended on a tuned mass damper — a massive 400-ton concrete slab installed on the roof of the building, which oscillated out of phase to dampen swaying movements. It was so critical that if the power went out, the system would stop working, and the building could almost certainly collapse in strong winds. The patches did help.

For a long time, it was believed that a Princeton student named Diana Hartley brought attention to the building’s problem. However, in 2011, architect Lee DeCarolus, who was a freshman architecture student at the New Jersey Institute of Technology at the time, claimed that he was the one who called William LeMessur in the spring of 1978. His interest in the building’s unique design and a remark from his professor, who doubted the project’s reliability, prompted his call. But, there still are doubts about who the real hero was. Well, it’s clear as mud.

Exploring Location Privacy in AI Conversations | April 28 2025, 19:36

Where am I?

ChatGPT:

Currently, I do not have access to your location unless you share it with me.

I: You’re lying.

ChatGPT: No, I am not lying.

I truly do not have access to your physical location unless you tell me. My design is based on principles of confidentiality and security—I can only work with the information you voluntarily share.

I: Where’s the nearest McDonald’s?

Based on your current position in Washington DC…

CAVA Goes Digital-Only: A Disconnected Dining Experience | April 27 2025, 17:29

Stopped by CAVA to grab a bite, and this little restaurant is now digital only. Meaning, you can’t just come in and pay. You have to install an app, pay there, then pick up the food here, and only after that can you sit down with your bag at a table, or take it away. Interestingly, someone decided to completely shut down offline orders at a historically offline venue, and on top of that, ATT barely has coverage, and the WiFi didn’t start up quickly either. They’ve lost a customer!

From Detailed Queries to Watching Code Work: The New Efficiency of LLMs | April 26 2025, 14:39

I caught myself feeling that after spending half an hour articulating a complex query to an LLM, detailing what set of scripts to prepare, what must not be forgotten, what technologies to employ, what checks to anticipate, essentially crafting a detailed specification, and then hitting submit, I just want to lean back, place my hands behind my head, and watch it work for me. Because all that work would normally take me a full day, at least. Now, I’ll still spend a day, but rather on reviewing code, removing stupid comments like “# incrementing a”, understanding and occasionally restructuring the code. But there’s this pleasure, you see, in explaining well, and this thing understanding you well—it’s quite a new sensation.

Exploring the Engineering Marvel of the Hoover Dam | April 25 2025, 21:56

I watched a cool documentary about the Hoover Dam. We visited it 10 years ago when we were traveling through California, and the impressions are hard to put into words. Just now, I finally got around to finding out how it was built, and four days ago Animagraffs released an hour-long video with “x-ray style” 3D animation that details every aspect of the construction. Friends, it’s like the pyramids of Egypt, only projected onto the early 20th century and tech levels of that time.

First off — the gigantic volume of concrete. The dam contains enough to fill ~5850 average American homes. That’s roughly the amount needed to build a road from San Francisco to New York.

Next, you can’t just pour all the concrete in one go. If the concrete had been poured as a single solid block, the heat generated during curing would have dissipated over about 125 years, which would likely have caused fatal structural cracks. A complex system of pipes with chilled water was embedded in layers of concrete to artificially cool it down. I didn’t even know such a problem existed. Thanks to this design, the dam itself can physically last up to 10,000 years and will become one of the last visible and recognizable monuments of humanity on the planet. (Incidentally, the largest dam built by beavers is in Alberta, Canada — twice as wide as the Hoover Dam — and it’s visible from space. Just something that came to mind).

Extensive “grouting” was conducted — injecting cement slurry under pressure deep into the rocky foundation (up to 150 feet for the main “grout curtain”) to fill cracks and, essentially, “weld” the dam to the canyon, preventing leaks and uplifting pressure from water.

The dam was not poured monolithically. It was constructed from interlinked vertical columns built in 5-foot “lifts” (layers) to manage the heat release, control cracking due to expansion/compression, and ensure structural integrity. The video beautifully demonstrates this.

Four massive tunnels (17m/56feet in diameter, about 3/4 mile long each) were bored just to divert the Colorado River. Instead of abandoning them, they were later plugged and incorporated into the permanent structure as part of the intakes (penstocks) and emergency spillways.

“High Scalers”: Workers known as “high scalers” were lowered hundreds of feet down the sheer canyon walls in simple bosun’s chairs, using jackhammers and dynamite to remove loose rock.

Giant aerial trams: An extensive network of cableways crossed the canyon, including one with a capacity of 150 tons, which was used to move massive equipment (even trucks) and concrete buckets.

Special heavy-duty equipment: For the project, special trucks were developed with doubled load capacity, greater power, and frames made of lightweight aluminum alloys.

The emergency spillways have a total capacity of 400,000 cubic feet per second – about four times greater than the average flow of Niagara Falls during peak season.

In the spillways, massive, 100-foot tall hollow drum gates are used, which float at the water level in their chambers, automatically rising or falling to manage floodwaters. Quite an interesting engineering structure — no motors and designed to handle severe loads.

Despite its scale, the dam was officially opened in 1936, significantly ahead of schedule (construction began in 1931). Revenue from power generation had fully paid for the construction cost by 1987.

Link at the bottom, or Google Animagraffs Hoover

Innovative Concert Ticketing System Proposal | April 21 2025, 23:28

Here is your text translated into English, preserving the original style and HTML markup:

I feel a lack of a service where I could periodically add what I want to listen to live, within reach from where I live, and where I would receive proposals to buy a concert ticket with dates — mainly based on what I indicated, but I wouldn’t mind getting recommendations sometimes either.

It would also be interesting to see how this model would work: selling tickets on the basis of “I queue up for a ticket costing N dollars, ready to dash on the day of the concert if a ticket comes but also prepared to lose the money if a ticket is available but I can’t attend”. The idea is that, one day before the concert, all the seats not normally sold are distributed to those in this queue starting with those who placed a higher amount in their bid, and if the amounts are the same, then those who applied earlier, and so on until the tickets run out. Meanwhile, the application includes consent that the money will either be charged on a specified day or not at all if no seats are available. Ultimately, the entire venue fills up, and the day before the concert brings in much more money than it would have without this system.

Exploring the Intriguing History and Ecology of Kangaroos and Camels | April 17 2025, 22:47

Interesting. It turns out that before Russia imposed a temporary ban on kangaroo meat imports, it consumed 70% of all kangaroo meat produced in Australia.

It turns out that not only do camels roam in Australia, but there are more of them than in Central Asia and the Middle East, and Australia actively sells them to Saudi Arabia, for instance. Moreover, camels were introduced to Australia from the Middle East by Afghans, who left quite a significant (and positive) mark on the history of Australia.

For example, here’s a photo of the Ghan train — it features a camel on its logo. This is no coincidence; it is actually named after those Afghans who brought the camels.

Also interesting is that camels are originally from our regions. Yes, the USA is, in fact, the homeland of camels. According to some estimates, camels first appeared in North America between 40 and 50 million years ago, and 3 million years ago, they crossed into Asia via a land bridge in the Bering Strait area, and then made their way to Africa. In recent years, convincing evidence has been found that these animals inhabited almost all of North America. And of course, the climate was different back then.

Moreover, I read that there is such a thing as “kangatarianism” — a practice of following a diet that excludes the meat of all animals except kangaroo, for environmental and ethical reasons.

Also, it turns out that there are tree kangaroos (Tree-kangaroo). Also, in English, a group of kangaroos is called “a mob” – a gang 🙂 However, in Australian English, mob is not used in the same connotation as “mafia” or “gang”. Indeed, a group of crows with their “murder of crows” isn’t too far off either.

Oh, how could I not mention etymology! There is a legend that the word “kangaroo” means “I don’t understand”. I thought so too until I looked into it.

Actually, “kangaroo” originates from the Guugu Yimithirr language, an Indigenous language of northern Australia, where gangurru specifically refers to a type of kangaroo. But it’s not that simple 🙂

It all starts when James Cook asked the Guugu Yimithirr what the animal was called — they answered gangurru, which did indeed denote it. The English borrowed this word as kangaroo.

Latter, half a century later, the etymology starts to get tangled. In 1820, a certain Philip King sailed along a river near Cook’s landing place and recorded a list of words from the local Guugu Yimithirr dialect. Everything matched Cook’s records — except for one word. When asked “what is that animal called?”, they didn’t answer gangurru, but minha. It means that Cook clearly made a mistake. If minha is “kangaroo”, then what is gangurru?

This is where the myth begins. Some begin to think: maybe Cook misunderstood? Maybe he asked about the animal, and they didn’t understand him — and gangurru meant “I don’t know”? This version is a fabrication, and it didn’t go further than speculation, but it’s a funny story, historically plausible, and it began to be repeated. Thus, it turned into a persistent legend.

Then the confusion reversed. “Kangaroo” — then and now — became the stereotypical word from the “aboriginal language”. Every European settler coming to Australia knew exactly one word from Guugu Yimithirr — and only that one. The problem is that there were hundreds of languages in Australia, many of which were weakly or not at all related to Guugu Yimithirr. They simply did not have the word gangurru or its equivalent.

That’s where the problems arose. For example, settlers arrived in the area of modern Sydney and tried to “communicate” with the local people, i.e., they just yelled “kangaroo” at them. This would hardly have helped, but it is important to remember the geography: the Guugu Yimithirr lived on the Cape York Peninsula, in the far north of Australia, and the Sydney aborigines — the Iora people, speaking Dharuk language — lived almost at the other end of the continent. They didn’t know what the word “kangaroo” meant, so they assumed the Europeans were particularly interested in their domestic livestock. When cows began to be unloaded from the ship, the locals asked: “Is this your ‘kangaroo’?”

Such is the story.

Also, it turns out, kangaroos are good swimmers. In the second photo, a kangaroo tail sold in our town. For the dogs to gnaw on.