Software · Infrastructure · Technical ownership
I connect software and infrastructureto create clarity.clarity.
Technical Lead — Software & Infrastructure
Full-stack & Platform Engineer · Laravel · Nuxt · Linux
Geneva, Switzerland · French / English
I connect software engineering, infrastructure and operational needs, with a focus on simple, robust and maintainable architectures.
A practical method
How I move from a problem to a maintainable system.
A short sequence for moving from an observed problem to a solution that can be operated and shared.
Notice a pattern
Something keeps being harder than it should be.
Build the smallest useful shape
Test a focused solution before turning it into a larger system.
Share what proves useful
Keep the durable parts as documentation, patterns or open source.
Step 0 of 0
Beyond application development
A cross-functional technical role.
I act as the primary internal technical owner for a small industrial company, covering business applications, Linux infrastructure, networking, internal support and security governance.
My scope spans company-wide business applications, internal infrastructure and the technical environments supporting systems delivered to customers.
Application engineering
Laravel, Nuxt, TypeScript and REST APIs supporting operational workflows from data models to production support.
Platform and infrastructure
Linux, virtualization, networks, deployments and monitoring across internal and production systems.
Technical responsibility
Technical decisions across software, infrastructure, support and security, with clear ownership boundaries.
Areas of impact
Where software, infrastructure and technical ownership create practical value.
Business systems
Full-stack applications supporting business processes, from data modelling and APIs to user interfaces, deployment and production support.
Platforms & infrastructure
Linux, virtualization, networking, deployment, monitoring and day-to-day operations.
Technical ownership
Coordination of technical decisions across software, infrastructure, support and security.
Reusable tooling
Open source packages extracted from recurring problems and maintained as documented, reusable components.
Open source, made concrete
A few tools that grew out of recurring work.
I publish focused packages when a pattern becomes useful beyond its original context.
- Forms across the stackFormForge and FormForge Client connect Laravel form definitions with Nuxt interfaces, validation and submission.
- Contracts that travelLaravel TypeBridge turns Laravel resources into predictable TypeScript contracts for frontend applications.
- Communication workflowsLaraMJML handles responsive Laravel emails, while NotificationCompass explores a clearer way to manage notification preferences.
- Small tools with a clear boundaryNuxt Typewriter packages a focused interface detail instead of making every application reinvent it.
Questions I keep returning to
The questions shape the work.
The questions I use to make technical choices concrete.
What compromise matters most?
Make cost, speed, flexibility and reliability explicit before choosing a solution.
Who owns this after launch?
Design for the people who will operate, evolve and maintain it.
What happens when it fails?
Recovery, observability and clear responsibility belong in the design.
What must remain possible?
Protect the processes and decisions the business cannot do without.
Let’s talk about software and infrastructure.
Explore the open source collection, or get in touch to talk through a technical system, interface or operational problem.