You depend on a system that predates the current team.
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.
A real senior specialist leads. Name on first reply. AI is a tool; a human checks the result.
01
What this problem looks like, how you can tell, and what is at stake if it stays.
What an unreadable legacy system does to a business, why teams freeze, and why mystery is not heritage.
The people who built it left. Comments are missing or misleading. One module talks to a database nobody documented. A small change takes weeks because everyone is afraid of side effects. Tests, if they exist, do not cover the paths that make money.
The team feels stuck and a bit embarrassed. New hires bounce off it. You keep postponing features because the foundation is a black box.
Software that earns money still needs a human who can change it. Mystery is not heritage.
You want a change, a fix, or a safe way forward — not a lecture on how the old code should have been written.
Legacy code nobody understands is still running invoices, bookings, or logistics. The problem is not that it is old.
Documentation, if it exists, describes a system that is no longer there. Tests, if they exist, skip the paths that make money.
These are operational signals, not aesthetic complaints about an old language.
Pull requests stall because nobody will approve a change in a module they cannot explain.
A tax rule, a new rate, or a partner file format should be a bounded edit.
The comments, or the wiki, describe a rule the running system no longer follows. Operators have private workarounds.
Only one machine, or one person, can ship. The steps live in a notebook, not in the repository.
When something breaks, the fix is 'restart this box' or 'run that script' with no written cause.
Before — if you leave it
If no one understands the system, you cannot fix a bug quickly, you cannot pass it on, and you cannot add the feature a customer already paid for. Eventually you will be tempted by a full rewrite that you cannot afford to get wrong.
After — if we close it
You get a map of the dangerous parts, a safer way to change what you asked for, and notes a future specialist can use. The system is still yours. It is just no longer a rumour.
Recognize your situation? Message us, we will sort it out.
02
Where this usually comes from, why it shows up in fast or AI-assisted work, and how to check it yourself.
Age alone does not make a system unworkable. Missing ownership and missing characterisation do.
The design lived in someone's head, a private chat, or a machine that was never inventoried.
Each urgent fix added a special case. After enough exceptions, there is no single rule to read.
What was easy to test was tested. The ugly, valuable path was left as a manual ritual.
A file drop, a queued message, or a nightly job still runs, and nobody can name the counterpart on the other side.
The team spent its energy arguing about a future stack and never invested in a map of the present one.
An assistant can summarise a file and still miss the stored procedure, the side-effect in a trigger, or the batch that runs at 2 a.m.
You can do a first pass without a rewrite plan. The aim is a map, not a judgement of the original authors.
What must work on a weekday: invoicing, import, export, login, the nightly run.
A running environment, even if fragile, tells you more than a frozen repo.
Pick a real request and see how far you get.
Cron, task schedulers, database jobs, and 'temporary' scripts in home directories are often the real application.
Backups, de-duplication, and a way to restore matter more than a new framework conversation.
Recognize your situation? Message us, we will sort it out.
03
A senior specialist leads. AI is a tool. A human checks the result.
Legacy is normal. Most lasting products have a core that grew under pressure. The problem is not that it is old. The problem is that no one now can stand for a change.
DevHero is Human First. A specialist with around 20 years of experience is used to reading unfamiliar systems and making a safe next step, not a fashion rewrite. AI can help search and summarise. A human decides what is load-bearing. An expert on payroll checks the result.
Around 20 years of experience is useful here because the work is judgement: what is load-bearing, what can be characterised with a test, and what should wait.
How a typical weekday case moves
Write on WhatsApp or Telegram. We take hard, unreadable systems when we can help.
Name the product, the stack if you know it, and the change or incident that is blocked. A repo or a staging URL helps.
Within a minute you should see the name of the person who will lead. They are alerted, and can be called if they do not respond.
On a typical weekday we aim to map the dangerous parts and make the change you actually need, or to tell you honestly if the next step is a larger rescue.
We read the running system, characterise the risky path, and make a change a human will stand for. A rewrite is a last resort, not a first pose.
We read the running system, the data, and the deployment, not only the repo myth. We identify the seams, add characterisation where it is risky, and make the change you need — or say if the next step is a larger rescue. We do not start a greenfield rewrite in a day.
Access, environments, jobs, and data matter as much as the repo myth.
We identify what is load-bearing for that change, not a complete encyclopaedia on day one.
A test, a script, or a recorded behaviour around the risky path, so the edit has a chance of being safe.
If the work clearly exceeds a session, we say so before we pretend otherwise.
The system should be a little less of a rumour than when we found it.
For a typical weekday case in scope, the aim is a map and a safer next step — not a new product in a new language.
A map of the parts that matter for your current request, including jobs and data if we can see them.
A change, or a clear reason why that change is not safe yet.
Notes on what we learned that the next person can use.
A human-checked result, and an honest recommendation if a rewrite or a longer programme is the real work.
A statement of what we did not have time to read.
Anything that helps us run or watch the system is useful. Do not send live secrets in the first message.
Plus any second repository that people forget: scripts, 'ops' folders, or a database project.
A staging URL, a VM, a compose file, or the person who still knows the ritual.
A business rule, a bug, or a launch that is blocked.
Cron, file drops, message queues, and the names of the databases.
Especially if the system is the only copy of the data.
First 4 hours with a specialist + unlimited AI: free, once per client. Further work is paid, on request. A human leads and checks the result.
Free (first session)
Larger work uses a different rate, on request. We say so before we continue.
On request
The base plan is weekdays only. Weekend work is a separate product. Any surcharge is stated up front, before any call, and depends on complexity. Amount: on request.
On request
The first session is free: the first 4 hours with a specialist, plus unlimited AI, once per client. Work beyond that, the complex-project rate, and the weekend rate are paid, on request.
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.
Recognize your situation? Message us, we will sort it out.
04
What not to do next, the stacks we see in this kind of work, and how to keep the fix in place.
Some popular moves spend a year and still leave you without a working path.
You will re-implement folklore and miss the exceptions that keep the business alive.
Generated translations look complete and can still drop a trigger, a rounding rule, or a nightly side-effect.
An emergency change should be rare and recorded, not the default workflow.
If production disagrees, production is the specification until you have characterised it.
The map can start with the next change you already need.
Tell us the language, the database, and how it is hosted. If we should not take it, we will say so.
PHP, Java, .NET, Ruby, Python, Delphi, and similar applications that still take orders or keep records.
Stored procedures, triggers, and large SQL Server or Oracle estates.
Cron, file transfers, ETL jobs, and message queues that nobody has drawn.
A modern front end talking to a core that predates the current team.
After a rescue, a few habits stop knowledge from leaving with the next person.
A short, current note in the repo beats a faded wiki.
A test or a recorded example is part of the change.
If only one machine can ship, that is still a risk.
Names, owners, and what happens if they stop.
A future stack is allowed. It is not a substitute for understanding.
They should see the job that makes money.
Recognize your situation? Message us, we will sort it out.
05
Straight answers about this problem, the session, and what happens next.
Only if that is truly the right move, and not as a default promise.
That is a usual starting point. We reconstruct enough behaviour to work safely, and we write down what we learned.
Tell us the stack in the first message.
Yes. A database that is also the application is a common legacy shape.
A freeze can reduce risk for a short period, and it can also freeze the business.
Write on WhatsApp or Telegram about the system and the change you need. No form, no web chat.
No. We will describe what we could read, what we changed, and what remains unknown.
They overlap. This page is for a system nobody understands.
Yes. Each client gets one free session: the first 4 hours with a specialist, plus unlimited AI as a tool. The 24-hour line is how quickly we aim to start and close a typical weekday case in scope, not 24 hours of unpaid work. Further work is paid, on request.
If a change is already blocked by code nobody understands, write on WhatsApp or Telegram. You will talk to a person.
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.