Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I hired a remote developer and I cannot tell if the work is going well

Short answer

You can manage a remote developer without reading code. Ask for working software you can open every week, a short written update, access to the code repository in your company's account, and a plan in small pieces with dates. If you only hear that it is almost done, ask to see it.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I get updates like it is going well, but I cannot open anything.
  • Deadlines keep moving and I cannot tell if the reason is real.
  • I do not know what has been built and what has not.
  • I am afraid to question the developer because I am not technical.
  • If the developer left tomorrow, I would not know what I own.

Why does this happen?

  1. Progress is invisible without working software

    Code is not something an owner can look at. Unless the developer shows the app running, updates are opinions.

  2. The scope is one large block

    A plan that says build the app gives no way to check progress. Small pieces, each ending in something you can try, make progress visible.

  3. The code lives in the developer's own account

    If the repository is in the developer's account, you cannot see commits or take the work elsewhere. GitHub lets an organisation give people roles such as read and write on a repository, so you can hold the repository and have the developer work inside it.

  4. Nobody agreed what finished means

    Without a short written definition for each piece, almost done can stay true for weeks.

What can I do about it today?

  1. Ask for a demo every weekA short screen share where you tap through what was built, on a real phone or the real site, not slides.
  2. Ask for a written update in three linesDone this week, planned next week, and anything blocking. Keep the messages in one place.
  3. Break the work into pieces you can testFor each piece, write one sentence: when this works, I can do this. Agree it before work starts.
  4. Put the code in your own accountCreate a repository under your company on a code hosting service and give the developer a role to work in it. The role page shows read, write and admin levels.
  5. Keep a list of every account the project usesHosting, domain, app stores, email service. Next to each, write who holds the login.
  6. Be polite and specific, not accusingAsk to see something rather than whether it is true. A good developer is glad of clear questions.

When should I bring someone in?

  • Deadlines have passed more than once and you cannot see why.
  • The developer refuses to show the code or the running app.
  • You suspect the quality is poor but cannot judge it.

How do I handle it?

  1. Review what existsI read the code and run the app, then tell you in plain words what is built, what is missing and what looks risky.
  2. Turn the plan into checkable piecesI split the remaining work into steps with a one-line test each, so you can see each step is done.
  3. Set up the reporting rhythmA weekly demo and a short written update, with the list of accounts and who holds them.
  4. Sit between you and the developerIf you want, I translate questions both ways and tell you when an answer does not add up.
  5. Say honestly if the project is in troubleI tell you what the problem is and what options you have, including stopping.

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?

How do I check the developer is actually working?

Look at what they show you each week. Working software and a repository with regular changes tell you more than hours reported.

Should I track their hours?

Hours show effort, not results. I suggest tracking finished pieces instead.

What if I do not understand the answers?

Ask for them in plain language. If that is not possible, a second technical opinion is worth having.

Can you manage my developer for me?

I can act as your technical lead for the project, reviewing work and reporting to you in plain words.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.