Architecture and code review.
A big decision is coming: rebuild everything, change hosting, handle more traffic. Before you make it, I read the code, the data and the servers, and hand you a clear document: what works, what does not, what the status quo costs, and in which order to act.
Remote, anywhere in France and abroad.
Sounds familiar?
You have been offered a full rewrite, and you want a second opinion.
Traffic is growing and you do not know whether the system will hold.
You are buying software, or a company that builds it, and you want to know what the code is worth.
Nobody on the team has an overall view of the system anymore.
How I go about it.
- 01
A complete reading
Code, data model, hosting, deployments, security. I read everything, and ask questions of those who know the history.
- 02
A document, not a list of complaints
What works, what does not, and above all what to do, in which order and for what effort. Each point says why it matters.
- 03
A meeting to decide
I present the document to your team, we discuss priorities, and you leave with a plan you can follow, with or without me.
What I have already done.
Real projects, in production. Each one gives the context and what I did.
Search API for a marketplace
Several million listings served from memory, without touching the database. Back office and performance.
Data model rebuild of an agricultural SaaS
Rebuilding the core domain of a product already in production, and migrating it without downtime.
GPS position processing engine
Taking over and rewriting a processing engine, with regression tests against the existing behaviour.
In practice Review of the repository, the data model and the infrastructure. Written report, then a meeting to go through it with your team.
Frequently asked questions
- Do I need to give you access to the code?
- Yes, read-only: the code repository, an anonymised copy of the database if possible, and access to the hosting. A non-disclosure agreement can be signed before we start.
- Does the review commit me to hiring you afterwards?
- No. The document is written so that your team, or another provider, can use it without me.
- What if the review concludes everything must be rebuilt?
- Then it says so, with the reasons and a plan to get there without stopping the service. It is rarely the conclusion: most often, a few targeted pieces of work are enough.
- Do you work remotely?
- Yes, anywhere in France and abroad, in English or French.
Let’s talk about your project.
Describe the situation in a few lines: reply within two working days. The first conversation happens by video, with no commitment.