Not too bad… :D

https://feditrack.javahippie.net/activities/dc0f534a-1ade-4bc4-8cf2-d9a8e017b925

All the carbs. #running #runnersOfMastodon

Mein Sohn letzte beim Bergwandern: „Wenn die Waden zu machen, ist der Lat dran“ und stürzt sich in die Stöcke.

Klar natürlich Siegfried auf der Couch „Die Frauen sind ja viel erschöpfter als die Männer“ … Alter, dein E-Bike brennt dir vor der Hälfte des Berges durch.

Das #TdfFemme stage 7 finish auf dem Mt. Ventoux bei über 30°, unfassbar wie Kasia Niewiadoma gefahren ist. 👸

@rotnroll666 @rationalgarde @UschiAachen

1) Es gibt (so schnell) keine zusätzlichen LKW. Werden die vorhandenen mehr gefahren, gibt es auch mehr Verschleiß, mehr Werkstattzeit, mehr Ersatzteilmangel.
2) mehr Waren auf den Straßen verschleißt auch die Brücken stärker. Umso mehr Brücken gesperrt werden, desto stärker werden die verbliebenen belastet.
3) pro jahr gehen 30000 lkw fahrer in rente, 15000 neue werden ausgebildet.
4) durch fahrtenschreiber sind speditionen eine der wenigen branchen, wo die arbeitszeit wirksam kontrolliert wird. Die fahrer machen beteits jetzt so viele touren wie überhaupt möglich ist.
5) wenn wir zitronenfalter zu zitronenpressen umschulen, können wir den Rhein mit zitronensaft füllen.
6) zwei drittel des binnenachiffsverkehrs sind gas und öl. Wird das auf LKW geladen, dann transportieren 80% der lkw den diesel, der zum betreiben all der lkw benötigt wird (in der ddr hat die eisenbahn fast nur die braunkohle transportiert, die benötigt wurde, um die züge zu betreiben, die braunkohle transportieren).

Weil ich statt PayPal mehr Banküberweisungen nutzen wollte, habe ich eine Webapp gebaut, die Girocodes generiert. (derzeit Betaphase)

Girocode ist ein QR für SEPA-Überweisungen, den viele Banking-Apps verstehen (z.B. im Feature „Foto-Überweisung“).

Workflow:
- Girocode generieren
- zeigen oder teilen
- Geld per Überweisung bekommen, per Echtzeitüberweisung sofort

Daten werden nur in deinem Browser gespeichert. 🔒

#did #dut #didit #dutgemacht

https://moritzglantz.de/girocodr/

Ich bin auch gerade aus meiner geschützten Umgebung ausgebrochen.

@duke_of_germany rofl, show me one handy man who had to stop working because they reached their "session limit" with their hammer 🤡

Updated my W8BEN to make sure I only pay 42% German taxes on my US stock options when they vest. And when I sell them, I pay another 25% German capital gains tax on the realised gains. Because no matter how you make your money, Germany takes around half of it. Unless you are rich enough, then you pay close to nothing ;) #TaxTheRich the way you tax me, Germany!

1/2

A few thoughts on this new trend of AI reviews.
For those that are unaware, if you submit a patchset to the linux kernel mailing list, as of recently, you will get ai reviews by a bot called sashiko.

My experience as a developer with it has honestly been rather negative.
Sashiko will generate way more comments than a human would, all pointing out potential problems with your patches.

This has, for one, an impact on your morale. Your code is being absolutely shredded apart by a bot which isn't fun.

On closer inspection though a lot of the comments are based on very shallow and inexact reasoning. They may look plausible and clever while being completely wrong and meaningless.

So for one one must go through all of them and carefully judge each comment. Blindly applying the comments can lead to outright broken code, but at the same time among the comments there might be genuine problems being pointed out so ignoring them won't do either.
The comments are not the result of proper reasoning but there's enough of reasoning like logic in them that it takes significant cognitive load to judge them.

But then, if I'm submitting code to the kernel there might be things I'm unsure about, the kernel is huge and not every submitter will know the intricacies of every kernel API.

Reviews generally play an important role there. If someone experienced points something out I can generally trust it and, even if the advice turns out wrong we can collectively take responsability for it and reason about it again when the bug shows up.

But if the bot points out something about code I was dubious about, what should I do? Did human mantainers not point out the bug because the bot did and agreed with the comment? Did they just not notice either the bug or the comment? Should I just blindly trust potentially wrong advice? Should I ignore potentially good advice? If it goes wrong the bot can't be held responsible for it, only I can, so maybe ping human mantainers? But then on top of me having to do more work to sift through the huge volume of comments human reviewers need to spend more time carefully analizing those comments. In the end it adds more friction and more work for everyone involved, and it's non trivial.

Arguably the end result might be better, among the many comments the bot makes there could be some genuine bug or security vuln that might have gone unnoticed. But at what cost? The cost is huge and I'm not even getting into the environmental implications and whatnot.

As far as I'm concerned I'd rather go back to the old workflow where comments I got in my patch where all meaningful and an opportunity to learn. Merging bugs has always been a part of the game and trying to preemptively prevent them is infeasible anyway.

What good is it to have a dubious and marginal improvement in the final code quality if the price to pay is making the process so much more exhausting and un-human for everyone? What impact will that exhaustion have on the code long term? It may very well be a net negative.

If someone really cared about the potential bugs sashiko can catch they should run it on the codebase themselves and do the work of sifting through the noise out of choice. Even then, filtering without enough care can lead to needlessly burdening patchsets that mantainers have to review.

#TdFFemme einfach spannender als #TdF.

Wenn’s ein Junge wird, nenn ich es Frenchie #Urlaubsbauch

I set myself a goal this year to get my ass up Alpe d'Huez on a bike but because my body wouldn't let me I had to abandon this goal.

Living on the coast as far away from anything you can call a mountain, I decided to create a mountain climbing challenge from what I do have near me, the South Downs.

I also decided to open it up for other folks and you can find the details here https://ziggyzaggy.greg-woods.tech/zigzag/.

Happy ZigZagging!

#southdownszigzag

@distincteclare @arrasz @rotnroll666

https://www.medico.de/presse/2026/chemische-kriegswaffen-zerstoerung-in-nahost

RE: https://social.tchncs.de/@Frau_Sofa/117039067359841520

Was für Bastarde, von den besten gelernt würde ich sagen. Als Nächstes dann Agent Orange oder was?

RE: https://mstdn.social/@dadamsda/117041274251861818

„festliche Animationen“

Alter, was rauchen die?!

@rotnroll666 @ewolff
Indeed a very interesting thread by @jens@social.finkenhaeuser.de

One funny detail, Firefox used as an example for too complex legacy software is a rewrite 😬
(implicitly addressed in the thread)
And Chromium (khtml, WebKit) again rewrites

In some way this reminds me of the story in The Deadline by Tom Demarco.
If a rewrite/incremental changes are worth it is highly project specific and probably unknowledgeable upfront

RE: https://social.finkhaeuser.de/@jens/117035905068742540

Cc @ewolff @realn2s great thread fitting ours yesterday

@samir @ewolff @jlink @rotnroll666

In this part of my talk on systemic effects of LLMs in teams/companies, my take is that in most teams that didn't practice co-creation (pair/ensemble programming), we already had what LLMs are driving to the conclusion.
From erosion of a shared mental model to a complete dissolution.

https://youtu.be/eEA0gJnWLh0?t=1847