I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.

I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).

It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.

The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.

We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.

I worry.

Several years of Deutsche Bahn business travel taught me something unexpected: eventually you stop fighting the system and start learning its moods, failure domains, and hidden virtues.

I wrote down the practical folklore that actually helps: apps, routing habits, delay survival, seat choices, fallback lines, and the strange civilisation of the Bordrestaurant at 250 km/h.

“A Field Manual for Three Years on Deutsche Bahn”: https://blog.hofstede.it/a-field-manual-for-three-years-on-deutsche-bahn/

#travel #db #trains #bahn

Est-ce que quelqu'un ici connaîtrait un-e médecin généraliste ou gynécologue qui pratique la pose de stérilet sous anesthésie locale ? Rennes, Brest, Nantes, Laval...
(Dans des délais raisonnables si possible)

 Retoot please je suis assez désespéré 

PS : læ premier·e qui me réponds que ça va, on peut supporter une pose de stérilet avec un médicament ou une crème anesthésiante, finira dans mon blokédex.

#Rennes #Bretagne #Brest #Nantes #Laval #JeCherche #doctoctoc

Are there people here that have examples of #opensmtpd filtering and/or adress rewriting ?

I am interested in two cases :

- want to block mail pretending to originate from my own domain (without breaking my own conf' ofc)

- want to rewrite all mail directed towards the dk tld so that it looks like originating from my dk domain (this is a simple rewrite of the address, I am legit owner and the MX is legit sender/receiver)

#email #filtering #openbsd

Je cherche à emprunter un vélo cargo pour pouvoir transporter ma fille ..

Édit: trouvé

Vegans are called difficult for refusing to participate in animal exploitation, but the real difficulty is living in a society built around it.

https://open.substack.com/pub/herbivoreclub/p/how-vegans-navigate-a-world-built

Ed Horley shared a nice overview of new #IPv6 tools from HexaBuild:
https://www.howfunky.com/2026/05/some-new-ipv6-tools-to-explore.html

Not another abstract discussion about why IPv6 matters, but tools that help with learning, planning, validation and real implementation work