Prerequisites
Code repository, build procedure, service and user description, known incidents and hosting constraints. Focused interviews complement code inspection.
Auditing existing code, architecture choices, legacy migration, code review — I bring a senior perspective to help you make the right technical decisions, before or during a project.
Based in Raismes, near Valenciennes, available for consulting assignments across the Hauts-de-France region — Lille, Douai, Maubeuge, Cambrai — or fully remote.
Before a takeover or a major change, an audit connects technical symptoms to business risks: a fragile workflow, an unmaintained dependency, manual deployment or missing tests. Recommendations are ordered by usefulness and dependencies.
Code repository, build procedure, service and user description, known incidents and hosting constraints. Focused interviews complement code inspection.
Component and dependency map, evidence-backed findings, prioritised risks and phased roadmap. Architecture decisions explain options, trade-offs and conditions that could invalidate them.
Review with your team using reproducible examples. Each priority action has an expected outcome and a verification method; a prototype can resolve major uncertainty before implementation.
The diagnostic can be followed by implementation support, code reviews or handover to your team. Follow-on work is scoped separately. Initial reply within 48 business hours, quote after scoping.
Two documented personal decisions: a .NET facade in front of Navidrome and a Flutter journal without a server. They address different constraints with explicit limitations.
A code audit assesses the quality, maintainability, security and performance of your existing codebase. I deliver a structured report listing the risks identified, their severity and my prioritised recommendations — without needless jargon.
Yes. I can step in on a consulting basis alongside an existing team: architecture review, code review, pair programming, best-practice training. On-site in Valenciennes or remotely.
Migration starts with mapping the existing system and its dependencies, then defining the target. We then proceed in incremental steps: strangler pattern, progressive rewrite, regression testing.
Depending on the engagement: a detailed audit report, architecture diagrams (C4, UML), ADRs (Architecture Decision Records), prioritised recommendations, a technical backlog or a migration plan. Everything is documented and reusable by your team.