Help for owners
Many different contractors have worked on my app and I cannot tell how good the code is
Short answer
Code touched by many contractors tends to have several styles, duplicated logic, missing tests and unclear ownership. You can judge it without reading code: ask whether it builds from scratch, whether it has tests, how releases happen and who understands it. An independent review turns that into a written risk list.
Does this sound like your situation?
- Each new developer says the previous one did it wrong.
- Simple changes take far longer than they should.
- Nobody dares to touch certain parts of the app.
- Fixing one bug creates another.
- I cannot tell whether the cost of keeping the app is reasonable.
Why does this happen?
Each person worked in their own style
Without shared rules, every contractor structures things their own way. The result is several approaches side by side in the same app.
Knowledge left with them
When someone leaves, the reasons behind their decisions go too. The next person sees only the result.
Nobody was responsible for the whole
Contractors are hired for a task. Keeping the whole tidy is nobody's job, so problems accumulate.
No checks to catch mistakes
Without tests and reviews, errors are found by customers. Developers then become afraid of change.
Short-term fixes became permanent
Temporary workarounds stay, and later work is built on top of them.
What can I do about it today?
- Check you own the codeMake sure the repository is in your company's account and that every contractor's access is known.
- Ask whether it builds from scratchAsk someone to build the app on a clean computer from the stored code. If that fails, the code is at risk.
- Ask what is tested and how releases happenAsk whether there are automated checks and what the steps are from code to the live app.
- List who knows whatWrite down which parts each past contractor worked on and whether anyone current understands them.
- Hold off on a rewrite decisionDo not decide to rebuild or to keep going until you have an independent view. Both can be expensive mistakes.
When should I bring someone in?
- You are about to invest more, sell, or hand the app to a new team and need an honest read first.
- Your current developers disagree on whether to fix or rewrite.
- You suspect security problems but cannot tell how serious.
How do I handle it?
- Read before judgingI check how the app builds, how it is structured, how data is handled, how releases happen and what protection exists.
- Look for the risks that matterSecurity gaps, missing backups, unmaintained packages and single points of knowledge come first, not style preferences.
- Write the findings plainlyA written report separates what is sound, what is risky and what is simply untidy, with the reason for each.
- Offer ordered optionsI describe the choices, such as keep, repair in stages or rebuild parts, with the effort and risk of each, and leave the decision to you.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Do I need a rewrite?
Not necessarily. Many apps with messy code can be improved in stages. A review tells you which case yours is.
Can a non-technical person judge code quality?
Not by reading code, but the questions above reveal a lot: does it build, is it tested, how is it released and who understands it.
Will a review criticise my earlier developers?
It describes the code and its risks, not people. Findings are about what to do next.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.