Posted by jpluimers on 2021/12/10
It has been a while after my last post about me having cancer. No, I am not giving up. But I am having the regular fear of the upcoming checks: did the metastases return, or do I have the luck to outlive some 30% of my peer group.
The last metastases surgery has been slightly more than a year ago. A year from now, that percentage hopefully will be 50% and slowly increase over time until about 90% in some 9 years from now.
At year’s end, I will know for sure.
Below are some links on, mostly Dutch but with English abstract, articles about the mental side of having cancer, or having survived it for now.
Read the rest of this entry »
Posted in About, Cancer, LifeHacker, Personal, Power User, Rectum cancer | Leave a Comment »
Posted by jpluimers on 2026/05/27
Got an error when pushing a relatively large commit to GitLab: error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
There was no big difference in information between these commands¹:
git push
git push --verbose
Read the rest of this entry »
Posted in //e, 6502, Apple, Apple ///, Apple IIgs, Apple ][, Development, DVCS - Distributed Version Control, git, GitLab, History, Power User, Software Development, Source Code Management, Versioning | Leave a Comment »
Posted by jpluimers on 2026/05/27
After the 2022 GitLab.com backlash* to auto-delete “inactive” (for whichever metric of “inactive”) repositories of free users, I thought they would have multiple checks in place to prevent that from happening.
TL;DR: of two possible checks to prevent this, only one is in place.
This means that if by accident one of those checks stops working, all inactive repositories will be be deleted after a 7 day retention period. Which is very short, especially when you miss the email about it (for instance because of holiday or health reasons).
That bad!
How/why I found out
Read the rest of this entry »
Posted in Awareness, GitLab, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2026/05/26
Interesting article: [Wayback/Archive] Stack Overflow’s forum is dead thanks to AI, but the company’s still kicking… thanks to AI – Sherwood News. with this important quote:
The complex questions still get asked on Stack because there’s no other place. If the LLMs are only as good as the data, which is typically human curated, we’re one of the best places for that, if not the best for technology.
I wonder about how far it has declined now, and also think these are reasons for the decline as well:
Anyway, the graph in that post is just a sexy version of a query you can create yourself on the SEDE (Stack Exchange Data Explorer). That’s why I included both below.
Read the rest of this entry »
Posted in AI and ML; Artificial Intelligence & Machine Learning, Database Development, Development, DVCS - Distributed Version Control, GitHub, GitHub Copilot, GitLab, LLM, Pingback, Software Development, Source Code Management, SQL, SQL Server, StackExchange, Stackoverflow | Tagged: edit, executionPlan, graph, messages, query, result, results, resultSets, site, SQL, switch, ThisIsWhyWeCantHaveNiceThings | Leave a Comment »
Posted by jpluimers on 2026/05/26
Posted in ChatGPT, Code Quality, Conference Topics, Conferences, Development, Event, Java Platform, Kotlin, Pingback, Software Development, Stackoverflow, Technical Debt, Testing | Leave a Comment »
Posted by jpluimers on 2026/05/25
A while ago, ejecting a CompactFlash card on Windows 10 failed with the dreaded message “The action can’t be completed because the file is open in COM Surrogate.”
I was in a hurry, and it was a long time since I bumped into a similar message, so I simply rebooted as I knew that for certainly would fix it.
Next time, these links will help me find which dllhost.exe process to kill:
Read the rest of this entry »
Posted in Power User, Windows, Windows 10, Windows 11 | Leave a Comment »
Posted by jpluimers on 2026/05/22
Waar altijd de PGB-houders onder vuur liggen, lopen vooral de grote zorginstellingen al jaren de kantjes af van Wlz maar declareren wel alles (vaak 4 maal het PGB tarief van een naaste), betalen de Wlz-“cliënten” volledige eigen bijdrage ook al ontvangen ze meestal veel minder zorg dan geïndiceerd.
Zorgcriminelen hebben dat gat ontdekt: dat kunnen zij ook, maar dan vloeit de winst af naar hunzelf in plaats van externe aandeelhouders van de zorginstellingen.
Die lezen dan ook de handleiding die bij [Wayback Zorgcriminelen richten zich op Wlz, zorgkantoren beloven actie – Skipr gelinkt staat, en volgen precies dezelfde stappen die reguliere zorginstellingen ook gaan volgen.
[Wayback/Archive] Handreiking-integriteit-gecontracteerde-Wlz-zorg-RIEC-ON.pdf [Wayback PDF View/PDF View]
--jeroen
Posted in Opinions | Leave a Comment »