| Keyoxide | https://keyoxide.org/aspe:keyoxide.org:KC2QQMSF6SUYM6TYT5OQ24HUFA |
| GitHub | https://github.com/jeromegamez |
| Website | https://jeromegamez.com |
| Keyoxide | https://keyoxide.org/aspe:keyoxide.org:KC2QQMSF6SUYM6TYT5OQ24HUFA |
| GitHub | https://github.com/jeromegamez |
| Website | https://jeromegamez.com |
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:
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 @_@
@derickr https://www.linkedin.com/posts/pronskiy_github-pronskiyphp-debugger-lightweight-activity-7438244638664196096-nUtg
This is a painful read.

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
Forge, a unified CLI for GitHub, GitLab, Gitea, Forgejo, and Bitbucket.