Skip to content
Antoine Le LouëtIndependent senior developer (Home)
Back to the Journal

Advice3 min read

An application built with AI: how do you take it over without starting from scratch?

Examine access and a demonstration flow, then choose a targeted fix without inferring code quality from its origin.

Replaying a flow narrows down the defect; a verified fix allows the component to be retained.
Observed behaviour helps decide what can be kept in the prototype.

Origin does not decide whether to rewrite

A generated application may already provide a useful service. Before handing it to a developer, prepare what is needed to understand its rules and run it outside the conversation that produced it. AI origin is part of the context; it is insufficient to decide whether to keep or replace a component.

This article’s case is fictional, written for the Journal lab on 19 and 20 October 2026. It is presented neither as a v0 export nor as client experience. A small request filter lets us run a flow and then a fix from a fresh temporary folder.

Prepare the takeover request

  • Code: accessible repository or export, reference commit, versions and lockfiles.
  • Accounts: owners of the platform, hosting, database and external services; permissions actually checked.
  • Data: schema, migrations, fictional dataset and recovery procedure.
  • Configuration: referenced variables, the role of secrets and an authorised way to obtain them.
  • Generation: tool and date, model if known, useful prompts and significant manual corrections.
  • Decisions: validated business rules, prototype shortcuts and uses not yet verified.

The GitHub features documented by v0 can help version the code. Their availability and required permissions must be confirmed for the account used. No v0 access or export was tested here.

Preserve the defect before fixing it

In the lab, filtering requests with status 1 returns one row, but status 0 returns both rows. The function tests the parameter’s truthiness: zero is treated as absent. Assertions observed this behaviour under Node.js 24.13.0.

Diff · executed fix
- status ? rows.filter(x => x.status === status) : rows
+ status !== undefined ? rows.filter(x => x.status === status) : rows

The fix preserves the function and clarifies the absent-filter contract. Cases for zero, one and no filter then passed. In this example, the defect lies in the filter condition: no component replacement is needed to satisfy all three cases. The lab cannot assess the quality of any particular generator.

Decide using observable criteria

Keep a component when its role is understood and its behaviour verifiable. Fix a targeted defect when the rule and change boundary are identified. Consider replacement when an inaccessible dependency or specific constraint prevents meeting the need, comparing migration costs and risks.

To start a real takeover, pass on the inventory and a flow you want preserved. Flag missing permissions and decisions still implicit. The first assessment should produce findings and unknowns, then an intervention acceptable to the person who knows the business.

Sources and useful links

Share on LinkedIn (new tab)

Keep reading
All articles in this category