EN · Engineering
Refactoring and code quality
I make existing software easier to understand and change, in small shippable steps, while it stays in production.
- Who it is for
- Teams with applications that are hard to change, poorly tested or dependent on one person.
- Where
- Pavia and Lombardy on site by appointment, across Italy and Europe remotely.
- How it starts
- A call, then a written proposal with scope, timing and cost.
Problems I solve
- Fear of touching the code: no tests on current behaviour.
- Unmeasured technical debt: nobody knows where to start.
- Tightly coupled modules: every change breaks another.
What you get
- Technical debt map with priorities
- Characterisation tests on current behaviour
- Refactoring in small pull requests, reviewed with the team
In practice
I make existing software easier to understand and change. Tests first around current behaviour, then small steps: clear module boundaries, fewer dependencies, less technical debt. The system stays in production the whole time.
- Technical debt map and priorities
- Characterisation tests before touching code
- Extracting modules and services where it makes sense
- Pairing with the team on reviews
Technologies
- PHP
- Python
- JavaScript
- Laravel
- Git
- CI/CD
- Test automatici
How I work
- Listening A call to understand the context, the problem and the constraints. No commitment.
- Proposal Scope, timing and cost written clearly, before anything starts.
- Delivery Small shippable steps, regular updates and code in your own repository.
- Handover Documentation and training: the work ends when your team can run it alone.
Related services
- Replatforming and cloud migration
Rehost, replatform or refactor: the right choice for each application.
- Assessment and second opinion
A review in a few days: clear priorities and a plan.
- Home automation and IoT
Connected devices, automations and data: from home and office to the edge.
Let's talk
Tell me the situation in a few lines and I will reply with possible next steps.