Discovery call
We map the terrain together — goals, constraints, what success actually looks like at the summit.
Four phases, two-week rhythm, no surprises at altitude. Each camp is a moment to look back at the route, check the gear, and agree on what we're carrying up next.
We map the terrain together — goals, constraints, what success actually looks like at the summit.
Architecture, API contracts, sprint plan and milestones. A written route before we leave base camp.
Two-week sprints with weekly demos. Tests at every camp, deployable trunk, no surprises.
Documentation, infra runbook, a 90-day support and the team owning what we shipped.
Security patches, performance monitoring, minor evolutions and on-call support. The route stays open long after the summit.
Goals, constraints, success criteria.We map the terrain.
Architecture, contracts, milestones.We plan the route.
Weekly demos, tests at every camp.We ascend step by step.
Docs, deploy, training, support.We reach the summit.
Patches, monitoring, evolutions.We keep the route open.
Already have a process? I fit into it. Six years of missions means six years of adapting to different teams, tools and rhythms — I know the gear.
Six years roping up with PHP and Symfony on production loads — fintech at 30 000 users, a telecom internal platform, and the patient kind of refactor that makes a 9-year-old monolith breathe again.
AI doesn't replace the developer it multiplies them.
The next frontier is agentic development.
Routes I've climbed end-to-end fintech APIs at production scale, telecom platforms, and the patient refactors nobody puts on a press release.
Playwright end-to-end test suite set up from scratch on a Laravel billing SaaS covering the critical flows of 13 000 entrepreneurs, via Sqwer.
Symfony & API Platform backend orchestrating investment flows for 30 000 active users RabbitMQ workers, Kubernetes pipelines, zero-downtime releases.
Maintenance & full refactor of a legacy mobile / IoT fleet manager PHP procedural → API Platform + Vue.js, dockerised, GitLab CI, SCRUM.
First climb. Maintenance & internal apps for the brand-and-listed-company registry, plus the database that fed them. WordPress backbone, custom tooling on top.
Code doesn't just run it consumes energy, handles people's data, and outlives the sprint that shipped it. These aren't policies bolted on after. They're part of the route.
No third-party trackers, no fingerprinting, no analytics that follow users across the web. Data stays local or on your servers never sold, never fed to ad networks. GDPR-aligned, always.
Every HTTP request has a carbon cost. Servers — this portfolio included — run on renewable-energy infrastructure. Performance and efficiency aren't just UX: they're the smallest footprint at altitude.
Code shipped today will be read, debugged, and extended in three years. Clean architecture, tested paths, no clever hacks that look smart until they don't. Maintainability is the long-term summit.
Tools, data and infrastructure that stay in Europe. No GAFAM dependency baked into the architecture — open-source stacks, EU-hosted storage, vendors that answer to European law.
Currently roping up for missions starting Q3 2026. Long-form asynchronous email preferred calls scheduled after a first written exchange.