French software developer. Day to day I work as a senior PHP / Symfony developer. I also design and ship tools end to end, and I care as much about permissions, failure modes, and operations as about features.
This public GitHub portfolio is recent. The projects shown here were developed over time on my personal self-hosted forge, then prepared and published as a selective public showcase. They are not my full body of work. GitHub creation dates are not the full development history.
- Problem first. Start from a concrete need, ship a usable product, document setup and limits.
- Security by construction. Least privilege, explicit allowlists, secrets out of the repo, irreversible actions constrained or confirmed.
- Agents with guardrails. Tools for AI clients get bounded scope, clear defaults (often read-only), and audit-friendly behaviour.
- Honest scope. Prototypes are labelled as such. Public projects aim for reproducible builds, tests or CI, and stated limitations.
- Core: PHP, Symfony, PostgreSQL, SQL, Bash
- Also used in public work here: TypeScript, Go, Python, SvelteKit, Docker Compose
- Infrastructure literacy: Ansible, Caddy, Tailscale (as sources and targets in tooling, not as a product claim)
- AI integration (public): MCP servers, agent tool design, least-privilege tool surfaces
Stack choices follow the problem. Defaults favour open protocols and components I can replace.