Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My app is written in several programming languages and nobody owns it

Short answer

Several languages in one product are not always a problem; an unowned one is. First write down which part does what, where it runs and who can change it. Then decide per part whether to keep, document, merge or retire it, so that every piece has a named owner and a way to be rebuilt.

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

Does this sound like your situation?

  • Different parts of my product are in different languages and none of my developers knows all of them.
  • A fix means finding someone who knows an old tool.
  • Nobody can say what some parts do or why they exist.
  • A part stopped working and there was nobody to ask.
  • I am afraid to switch off any server in case it is still used.

Why does this happen?

  1. Each developer chose their favourite tool

    Different people were hired at different times, and each wrote their part in the language they knew best.

  2. Quick scripts became permanent

    A small helper written to solve one task turned into something the business depends on, but nobody treated it as part of the product.

  3. Experiments were never removed

    A trial of a new tool was left running, and other parts began to rely on it.

  4. The people who built it left

    When the only person who knew a part leaves, the part continues to run but is no longer understood.

  5. Nothing is recorded

    There is no map of components, servers and connections, so the real picture lives in people's memory.

What can I do about it today?

  1. Make a plain list of partsOne line each: what it is called, what it does for the business, where it runs and who last touched it.
  2. Mark what customers depend onTag each item as customer-facing, internal or unknown. Unknown items need a careful look before anything is switched off.
  3. Find the code and the loginsCheck that each part has its code in a company-owned repository and that its server accounts are known to you.
  4. Name an owner for each partEven an owner who is not a developer, such as the manager responsible for what it does, gives questions somewhere to go.
  5. Do not switch anything offUntil the list is complete, leave unknown servers and scripts alone. Something may depend on them.

When should I bring someone in?

  • You cannot get the list because nobody understands some parts.
  • A part that nobody owns is old, unmaintained or touches customer data.
  • You are considering merging everything into one language and need to judge the effort.

How do I handle it?

  1. Map the systemI trace how the parts connect, what each one does, where it runs and what data it touches.
  2. Judge each part separatelyIs it needed, is it maintained, is it safe, is it understood. Each answer is written down.
  3. Recommend keep, document, merge or retireNot everything needs rewriting. Some parts are best kept and documented, others replaced when there is a reason.
  4. Assign owners and write them downEach part gets a named owner, a build and deploy step, and a short description that survives staff changes.

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?

Is it bad to use more than one language?

No. Many products do. It becomes a problem when nobody understands or owns a part.

Should everything be rewritten into one language?

Usually not as a first step. A rewrite is costly and risky. Mapping, documenting and retiring what is unused often solves most of the pain.

What if the original developer is gone?

The code can still be read and described. It takes longer, which is another reason to start the map early.

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.

Next step

Want this off your desk?

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