Your Developer From 2019 Doesn't Answer Calls. His Code Still Runs Your Business

“I write these guides from what we see in production, not from what sounds good in theory. If something doesn't work for real businesses in the UAE, it doesn't make the page.”

The Hostage Situation

This isn't a technology problem. It's a business continuity crisis hiding behind the fact that the system currently works. "Currently" is doing heavy lifting in that sentence.

When something breaks, and something always breaks, you have two options. Find the original developer and hope he responds. Or hire someone new to reverse engineer code they've never seen, written in whatever style and framework the original developer preferred, with zero documentation.

Option one has a success rate of about 30% based on what we see in Dubai. Option two costs 3X to 5X what the original fix would have cost if documentation existed. A AED 2,000 bug fix becomes a AED 8,000 archaeology project because the new developer spends 80% of their time understanding the code and 20% actually fixing it.

One ecommerce company in Dubai Marina came to us after their payment processing failed on a Thursday evening. Their developer hadn't responded in 6 months. The payment module was a custom integration with no comments, no readme, no API documentation. Our team spent 3 days understanding the code before we could make a single change. Total cost: AED 14,000. Original bug: a 4 line fix that would have taken 20 minutes with documentation.

What Documentation Actually Means

Documentation isn't a 50 page manual. For most small to mid size custom software projects, proper documentation means four things. An architecture overview that shows how components connect. A database schema with field descriptions. API documentation for any external integrations. And inline comments explaining business logic, not what the code does, but why it does it.

This takes roughly 10% of development time to create. On a AED 30,000 project, that's AED 3,000 worth of documentation. The ecommerce company would have saved AED 11,000 on one bug fix alone if that documentation existed.

The Escape Plan

If you're currently in this situation, there are three things to do right now. First, get access to your source code. If you don't have the repository credentials, that's problem number one. Your code should live in your account, not the developer's. If he disappears, his personal GitHub account goes with him.

Second, commission a code audit. A technical review of your existing system that produces the documentation your original developer never wrote. This typically costs between AED 5,000 and AED 15,000 depending on system complexity. It gives any future developer a map instead of a maze.

Third, establish a maintenance agreement with a team, not a person. A single freelancer is a single point of failure. A development team with multiple engineers who understand your codebase means nobody's vacation or career change holds your business hostage.

Prevention Costs Less Than Rescue

Every new software project should include three non negotiable deliverables. Working code. Source code access in the client's own repository. And documentation sufficient for any competent developer to maintain the system without the original builder.

If your current developer resists providing these, ask yourself why. The answer usually reveals whether you have a partner or a dependency.

Do you have access to your source code right now? If you had to check, that's your answer.