Help for owners
I cannot tell if my developer is doing a good job
Short answer
You can judge a developer without reading code. Good ones show working software often, explain problems in plain words, keep your accounts and code in your name, and can tell you what is risky. If you still cannot tell, pay for a short independent review of the code and the setup.
Does this sound like your situation?
- I cannot tell if the delays are normal or a warning.
- Every question gets an answer I do not understand.
- I do not know where my code and accounts are.
- The costs keep growing and I cannot see why.
- I am afraid to ask for a second opinion.
Why does this happen?
You cannot see inside the work
Code is invisible to a business owner, so trust has to be built on things you can see: working software, clear notes and open access.
Updates describe effort, not results
Hours spent and tasks completed do not show whether the product moves forward. A demo does.
A developer who is good at code may not be good at explaining
Plain explanations are a skill. A developer who cannot say what is risky in words you understand is a risk by itself.
Quality problems stay hidden at first
Shortcuts rarely show in the first demo. They appear as bugs, slow changes and costs later.
What can I do about it today?
- Ask for a short demo every week or twoA working screen you can click on is the best sign of progress.
- Ask where the code and the accounts areThe answer should be a repository and accounts in your company's name, with you as the owner.
- Ask what the biggest risk is right nowA good developer answers in a sentence or two and does not say everything is fine.
- Ask how a change gets tested and releasedYou are listening for a clear, repeatable answer with a way back if something goes wrong.
- Notice how bad news is handledEarly warnings with reasons are a good sign. Silence and surprises are not.
- Do not sack or accuse because of a feelingGet an independent view first. A feeling is not evidence, and a relationship ended in anger costs you access.
When should I bring someone in?
- Deadlines slip and you are not told why.
- You are about to commit more money to the same developer.
- You want proof before a hard conversation.
How do I handle it?
- Review the code and the setup, not the personI read the code, the release process, the accounts and the hosting, and write down what I find.
- Report in plain languageWhat is good, what is risky and what to do about it, ranked by how much it matters to your business.
- Compare with what was agreedI check the work against the brief and the quote, so you know what the issue is: quality, scope or communication.
- Suggest the next stepContinue as you are, with changes in how the work is run, or move on in an orderly way. I do not need to replace your developer to give you a view.
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?
Will my developer be offended by a second opinion?
A confident developer usually is not. You can also describe it as a routine check of the setup.
Does the reviewer need full access?
Read access to the code and a view of the setup is enough. I do not need your passwords.
Can you tell if the price was fair?
I can say what the work involves and how large it is. Pricing is your decision, and I do not name figures here.
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.