At #SUSECon2026 it's all AI, Sovereignty and Resilience front and center, coloured in a hopeful green theme.
I got some new ideas already.
PHP Enthusiast. Former Perl Monk. Software Architect.
Housekeeping on fig/log-test package.
Somewhat composer/satis interested.
Blogs on all things Horde.
Likes trains and mountains and old castles.
At #SUSECon2026 it's all AI, Sovereignty and Resilience front and center, coloured in a hopeful green theme.
I got some new ideas already.
Github is strange these days. Repeatedly it happened that it left PRs open after I pushed rebase-merge and then refused to redo/close "Base branch has changed".
Used to be kind of a nice product.
Horde 6 RC phase is set to start on 2nd of may and there's so much left to do. So few evenings left.
I won't do this very often but it gave me a chuckle. First addendum says - "Biking lane closed". Second addendum says - "This also applies to bikers".
My car repair shop has "upgraded" its hotline from some old school press this for topic A to a dumb ai bot including fake keystroke sounds and delays on every answer. It doesn't know several domain words (hardly exotic) and tries really hard to turn me off when I ask for a human operator. It's taken 10+minutes to get into the 1-minute call with a human who adresses my need. Give me back elevator music and hold the line loops.
At work in an AI heavy environment I sometimes let the agent just try to implement some spec not with the goal of actually using that but to use it as an input for critique, especially when it gets stuck and tries increasingly zany hotfixes. Learning from failure is a thing but learning from AI failure is a thing, too