Ashish Pitrodafield notes
All plates

Field guide Plate 06

Takeover

The developer has gone, the handover was a repository link, and nobody left is sure what runs where. This is the job I get called for most often, and it is the one where reading carefully is worth more than typing quickly.

— picking it back up

I

Where it’s found

who this is for

The developer left

mid-build, or stopped answering. You have a repository, some credentials, and no idea which of the four branches is the one that is live.

An agency handed it over

and the handover was a zip file. It runs, but nobody in your organisation can change it, and the last quote to do so was surprising.

It works and nobody knows why

so nobody touches it. That is a business risk with a due date on it — the day something finally breaks and there is no one to ask.

II

Field marks

what the work actually is

  1. The audit

    What is running, where, on which versions, with which credentials, and what it depends on. Written down and handed to you — this is the deliverable, not a preamble to one.

  2. Getting it to run locally

    Reproducibly, by someone who has never seen it before. Until that is true, nobody can safely change anything, including me.

  3. Stopping the bleeding

    Backups verified, secrets rotated away from the previous developer, and anything actively broken triaged in order of what it costs you.

  4. Making it changeable

    Enough tests on the paths that matter to change things without holding your breath. Not full coverage — coverage where being wrong is expensive.

  5. Then, the actual work

    Finishing the build, or the feature you originally wanted. By this point it is an ordinary project rather than an archaeology dig.

III

Behaviour

how it runs

  1. 01Audit

    A fixed, short, paid piece of work that ends in a written document. Yours regardless of what happens next.

  2. 02Triage

    What is urgent, what is expensive, what is merely untidy — and the difference stated plainly.

  3. 03Stabilise

    The urgent items, in order, before any new feature is discussed.

  4. 04Continue

    Normal project work, now on ground that holds.

IV

What it costs

what decides the price

Nobody can honestly quote a takeover without looking first, and anyone who does is guessing with your money. So this one always starts the same way: a short, fixed-price audit that ends in a written document describing what you have.

That document is yours whatever you decide next — including taking it to a different developer. It is the only way I know to make the first step safe for someone who has already been let down once.

V

Questions

the ones I get asked

Will you tell us the previous developer was bad?
No. It is usually a project that ran out of money or time rather than someone incompetent. What you get is a description of the current state and what it will take — not a verdict on someone who is not in the room.
What if the code is genuinely beyond saving?
Then the audit says so, with the reasoning, and you have that in writing before spending anything further — which is worth the audit fee on its own.
We do not have all the credentials.
Common, and recoverable more often than people expect — domain registrar, host and DNS records leave a trail. Recovering access is part of the audit.

Send a note

Tell me what you have, what is wrong, and what it should do instead. I will tell you honestly whether I am the right fit.

Write to me or read the other plates