Fleur Kelpin

@fdlk
120 Followers
338 Following
2.1K Posts
Software developer, Mum, Gamer. Groningen
GitHubhttps://github.com/fdlk
Verhalen over buren met ruggengraat moeten verteld blijven worden, ook na 40 jaar. Om waakzaam te blijven en als voorbeeld. Opdat we β€œde moed hebben om voor elkaar op te staan, juist in de afwezigheid van de ander.” Een prachtige column en Eid-wens van Naeeda Aurangzeb in @Trouw:
Right Next Door (Because Of Me) van Robert Cray Band. Dit nummer draait tot 00:08:37.
😱

Married women: our right to vote is at risk if you took your husband's name.

Weirdly, I'd say this is going to encourage newly married women to keep their maiden names.

#VotingRights #USPol

Nog 5 uur en 35 minuten, dan is het weer lente!

On behalf of the team and everyone who has contributed, I'm happy to announce that Spring Boot 4.0.4 has been released and is now available from Maven Central.

https://spring.io/blog/2026/03/19/spring-boot-4-0-4-available-now

I hope it's not 404ing.

#java #spring #springboot

Spring Boot 4.0.4 available now

Level up your Java code and explore what Spring can do for you.

Spring Boot 4.0.4 available now
They never message back ☹️
#graffiti

RE: https://social.treehouse.systems/@swags/116235865719541791

Today was the SuperTux 0.7.0 release (yay!), but some of us were alarmed by the "Claude contributed to this repo" message on GitHub (oh no!)

Well, I've learned a few things from the discussion about this topic.

A single PR "co-authored by Claude" has slipped through. The code was written by a human (according to the commit), then properly reviewed and eventually merged by a maintainer. The Claude contribution is attributed solely to the code comments added through a mid-PR-flow commit update.

And now the commit history will show Claude as a contributor. It might be impossible to rewrite it. Rewriting kind of goes against the idea of having the git history, too. Even if that was possible, it's an extra effort which not all maintainers can prioritise.

So: seeing "Claude was here" in a GitHub repo is a "red flag", but it shouldn't be "therefore guilty of slop and LLM proliferation by default"; please use your head/best judgement.

I guess it is a cautionary tale for the maintainers, too