Jérôme Gamez 🐘

125 Followers
210 Following
1.6K Posts
Starting to think the real risk is not AI replacing junior staff, but senior staff quitting because they just can’t take this AI bullshit any longer and just opt for early retirement.
Perhaps the uncritical use of LLMs in our FOSS ecosystem is a symptom of burnout in our maintainers and projects.

Not sure how we went from plain, straightforward words to LinkedIn speak but now you can use Kagi Translate to fit right into that crowd:

https://translate.kagi.com/?from=en&to=LinkedIn+speak

When the outlook is so poor that you have to crack down on reporting about it, it's a sign you’re in an authoritarian system.

Software development teams, for the love of software engineering, STOP splitting frontend/backend applications into separate repositories!

The amount of bullshit contract-level testing that you have to do just because of this is enormous!

Being able to re-use the same code-level symbol across layers is an advantage.

And no, making a `shared` repository somewhere else just amplifies deployment issues @_@

AI Didn't Simplify Software Engineering: It Just Made Bad Engineering Easier

GitHub - pronskiy/php-debugger: Lightweight PHP debugger extension (forked from Xdebug, stripped to debug-only and optimized) | Roman Pronskiy | 11 comments

I forked Xdebug – stripped to debug-only and optimised to reduce overhead of enabled debugger in PHP from 300% to 5%. All (almost) done by feeding the Xdebug source code into OpenClaw and tinkering with it. What does this mean? PHP devs can keep this debugger running all the time and it won’t slow down the code. No need for all that fuss of turning the debugger on and off. On the other hand, is a step debugger even necessary in the world of AI agents? https://lnkd.in/egb83Tzw | 11 comments on LinkedIn

LinkedIn

Forge, a unified CLI for GitHub, GitLab, Gitea, Forgejo, and Bitbucket.

https://nesbitt.io/2026/03/13/forge.html

Forge

A unified CLI for GitHub, GitLab, Gitea, Forgejo, and Bitbucket.

Andrew Nesbitt
So AGENTS.md is just the human-readable documentation the AI dudebros have been refusing to include in README.md until now, because they claim that the code is "self documenting" and everyone else must be stupid if they can't figure things out.