loevborg

This comment makes me despair. Pair Programming and TDD, as well as other aspects of Extreme Programming, were explicitly introduced as practices that put the human, with needs and feelings, at the center of the software development process. Your analogy is wildly off base, so much so that I suspect a trolling attempt (if that's the case, well played)

7up is truly one of the most astonishing and ambitious pieces of television ever made. When I found it, I couldn't stop watching it and I learned a ton from it. Highly recommended!

Nelson was a pioneer of computing? No, he is a pioneer of computing.

I was on the island of San Giorgio Maggiore last year and was disappointed that I wasn't able to see the labyrinth. Also if I remember correctly the tower of the church wasn't accessible due to renovations. I'm glad to hear that the labyrinth is getting reopened. In general there's so much so see in Venice, and most of it is not overcrowded at all once you skip the top 10 sights that get visits by mass tourism.

I agree, same for foreign keys, triggers, higher isolation levels, the list goes on

DSQL looks like a Big Deal to me - solving the essential scaling bottleneck that relational DBs give you without ending up with a weird system like dynamodb that no one wants to use.

Why aren't more people talking about it?

Please go on. I also feel like asyncio is a big hack. Even just accidentally blocking the event loop is way too easy. And I couldn't believe it when I read that you need to store a reference to a task in a set to keep it from accidentally getting canceled. How did this become the main stack of AI backends? It's like node but slower AND much easier to mess up because of synchronous IO.

My advice:

- Don't use long-running transactions. They are a risk for db health. Only use transaction when you have a strong justification

- Set idle_in_transaction_session_timeout to prevent a long-running transaction from holding on to locks or tuples

- Set lock_timeout for migrations to prevent a single DDL statement to bringing down your system

- Set statement_timeout to prevent an expensive query from bringing down your system

I think you missed GP's point

Thanks for the link. As a longtime listener, listening to Bob Garfield's voice brought a tear to my eye - I'm a big fan and was sad when he left OTM, as much as I admire Brooke.

user: Do you think Germany will start a major war in Europe?

talkie-1930: No, I do not think Germany will start a major war in Europe. I think the war, if it comes, will be started by someone else. Germany may fight to prevent a war being started, but she will not be the starter. Germany has had enough of war.

Any services like this for Hetzner?

Sometimes TCP/IP is a leaky abstraction, and recently ipv6 peeked through in two separate instances:

- In a cafe wifi, I had partial connectivity. For some reason my wifi interface had an ipv6 address but no ipv4 address. As a result, some sites worked just fine but github.com (which is, incredibly, ipv4-only) didn't

- I created a ipv6-only hetzner server (because it's 2026) but ended up giving up and bought a ipv6 address because lack of ipv4 access caused too many headaches. Docker didn't work with default settings (I had to switch to host networking) and package managers fail or just hang when there's no route to the host. All of which is hard to debug and gets in your way

I don't think I get notified but maybe it's because my replies are unpopular

I agree. I wonder how people are motivated to comment if they can't even track replies or check likes. It certainly completely kills motivation for me