Looking for a team? It fits in this office.

I’m Xavier, a software and solution architect for 20 years. From the first idea to launch day, you only ever talk to me.

Book a call+33 6 35 33 10 46

  1. Software architect. Over 20 years shipping products.
  2. Direct line. No switchboard. +33 6 35 33 10 46.

The software architect’s office

Sheet 01 / 07

Scale
1 senior
Drawn by
X. Boubert

Resemblance to the pictogram: approximate.

They trusted me

How I work

I put twenty years of craft into a framework.

It brings together many AI agents and tools that share the work among themselves, the way nobody worked even two years ago. With them, I deliver tested code that meets the standards of the trade: TDD, DDD, hexagonal architecture, clean code, separation of concerns. Decisions and reviews stay in my hands.

  1. Agents working as a team. They split the work among themselves, tests and security included.
  2. The architect. Scopes, reviews every line and ships. One point of contact.

My framework, my expertise

Sheet 02 / 07

Scale
1 senior
Drawn by
X. Boubert

Team drinks after work: one attendee.

Software factory for your products

Tell me about your project, I’ll deliver the product.

Website, mobile app or desktop software, SaaS or internal tool: it all comes out of the same factory. You bring me an idea, a spec or a ticket. I set the architecture, then we move forward in agile iterations. I build with my framework, I review every delivery, then it goes through the tests and the security check. The code lands in your repository, the product goes live.

  1. Input. An idea, a spec or a ticket.
  2. Scoping. Hexagonal architecture, split by domain (DDD). The framework estimates the schedule.
  3. Review and security. I review every delivery. Tests and the security check run before it leaves.
  4. Your repository. The code is yours.
  5. In production. Web, mobile or desktop, your product live.

Software factory for your products

Sheet 03 / 07

Scale
1 senior
Drawn by
X. Boubert

Lost and found: one spec from 2019. Still unclaimed.

Legacy migration

We swap the parts without stopping the machine.

AngularJS, jQuery, PHP, untyped JavaScript, an unsupported Node version, a monolith grown too heavy: I move your application to maintained technologies, without rewriting everything at once. Scoping sets the order of the parts. I rebuild each one, helped by my framework, my experience and my best practices, then regression tests compare it with the old one. Your product stays live from start to finish.

  1. The legacy. Your application, on technologies that are no longer maintained.
  2. Scoping. I take stock of the legacy, set the order of the parts and adapt my framework.
  3. Test bench. Every rebuilt part goes through regression tests.
  4. New version. On maintained technologies, part by part.
  5. In production. Your product stays live during the migration.

Legacy migration

Sheet 04 / 07

Scale
1 senior
Drawn by
X. Boubert

The old machine has been told. It took it well.

Audits

I tell you where your software stands, and where to start.

Before you build, migrate or hire, take stock. My framework reads all the code. I check every finding and measure the gap against best practices: architecture, tests, security, technical debt. You leave with a complete report and a costed plan.

  1. Your system. Your application as it runs today.
  2. Diagnosis. The framework reads all the code. I check every finding against the standards.
  3. Priorities. Every risk is ranked, security included. We start with number 1.
  4. The plan. Costed, in order of priority.
  5. The report. Written for decisions, walked through with you.

Audits

Sheet 05 / 07

Scale
1 senior
Drawn by
X. Boubert

The report is short. On purpose.

Part-time or full-time architect

Your team gains a senior architect, without hiring.

Your team keeps its tools and its way of working. I take the architect’s seat, part-time or full-time: I make the technical calls, set up best practices (code reviews, TDD, agile) and share tools and practices from my framework with everyone.

  1. Your team. It keeps its tools and its way of working.
  2. The architecture. Kept up to date and shared with the team.
  3. Shared know-how. Code reviews, TDD, tools and practices from my framework, for everyone.
  4. The architect. Moves in with you, desk included. No hiring.

Part-time or full-time architect

Sheet 06 / 07

Scale
1 senior
Drawn by
X. Boubert

Delivered assembled. Compatible with existing teams.

Security rules

In every factory, security comes as standard.

Products, migrations, audits or an architect in your team: the same rules apply to every engagement, from the first scoping to the last delivery.

  1. By design. Security risks (OWASP) are handled from the scoping stage.
  2. A scan at every delivery. Dependencies, secrets and known vulnerabilities checked.
  3. Your data. No client data is sent to a public model.
  4. Limited access. Only what is needed, handed back at the end of the engagement.

Security rules

Sheet 07 / 07

Scale
1 senior
Drawn by
X. Boubert

Must be displayed in every factory.