Legacy code modernization
We move your legacy PHP application to a modern architecture without a rewrite, while it keeps running. This is also how we are migrating ONLINEKURUM.
Modernization and consulting
Software consulting
A second pair of eyes on architecture, technology choices and code quality before you decide.
We offer a second pair of eyes before you make an important decision about architecture, technology or code quality. We review your existing code and infrastructure and deliver our findings in writing, with prioritized recommendations you can act on. If you want, we help your team carry out the recommendations or set up a code review process. Consulting can be a one-time review or an assessment repeated at regular intervals.
The problem we solve
The cost of software decisions usually shows up late. The choice of a framework, a database structure or a hosting option looks small today, but a few years later it sets the cost of every new feature. A team does not always have the time to question these decisions. When everyone is busy with daily work, it is hard to look at the architecture from the outside, and familiar solutions are repeated without question. The same question comes up when buying new software or hiring a team: does this option really meet our needs? What is needed is an assessment that knows your system, shows its findings with examples, gives the reasons for its recommendations and makes it easier for you to decide.
How we work
-
Defining the question
Together we clarify which decision you are facing or which problem is bothering you. The scope and length of the review and the report you receive at the end are agreed in writing up front. With a narrow scope, the review is short and the result feeds straight into your decision.
-
Code and architecture review
We review the code, the database, the dependencies and the deployment process. Security issues, parts that carry a maintenance risk, missing tests and performance bottlenecks are noted with concrete examples. Where useful, we talk briefly with your team to understand why the code looks the way it does today.
-
Prioritizing the recommendations
We rank the findings by impact and cost. For each recommendation we write in plain language what should be done, why and in which order, together with the alternatives. Quick wins and long-term work are grouped separately, so you can take the first step right away.
-
Presentation and follow-up
We go through the report with your team and answer questions. If you want, we support the implementation of the recommendations or review progress with you at set intervals. In follow-up meetings we look at how many recommendations have been put in place and at the new questions that have come up.
What we deliver
- A review plan with a defined scope and length
- A written report that shows the findings with examples
- A list of recommendations ranked by impact and cost
- A closing meeting with your team
- A short action list for quick wins
Frequently asked questions
Do we need to give you access to our code?
Read access is enough for a code review. We use the access only during the review and recommend that you close it when the work is done. For confidential projects we can sign a non-disclosure agreement before the review starts.
Do we have to carry out the recommendations?
No. The report is written so that you can make the decision. You can carry out the recommendations with your own team, with us or with another team. Because the reasons for each recommendation are written down, whoever carries it out knows what is done and why.
How do you set up a code review process for a team?
We propose a review flow that fits the way your team works: which rules changes are reviewed against and by whom, what the automated checks catch and a shared coding standard. In the first weeks we take part in the reviews with your team and help the process settle in.
Do you also help with choosing technology?
Yes. When you choose a framework, a database or hosting for a new project, we compare the options against your needs, your budget and the knowledge of your team. We set out the cost, risk and maintenance effort of each option, today and in the future, in writing. That way the decision rests on reasons, not on a preference.
Get a second opinion
Describe in a few sentences what you want to build. We review your needs and write back with how we can move forward.