old code /

Old code.
New life.

Menu
@temrjan ↗

Clarity.
A plan.
A next step.

Audits and development for existing systems

Old Code / 001

For systems that already work

Old code.
New life.

Find what is holding your project back. A free review of one agreed area: security, complex code or architecture.

Start with a free audit See a sample report

Start with a description. We will discuss code access later.

An illustration of audit areas

01 / Choose where to start

One question.
Three directions.

Choose what matters most to your project. Unsure which area to pick? Start by describing your situation.

01

Security

Who can see
your data?

We review one access scenario: how the system identifies a user, checks their permissions and returns data.

You receive → confirmed issues, the conditions that trigger them and recommendations for fixing them.

Review access
02

Refactoring

Why is the code
hard to change?

We examine the difficult area, its dependencies and behavior checks to understand what makes small changes risky.

You receive → a plan for small improvements: what to keep, what to simplify and which tests are needed.

Review a difficult area
03

Architecture

How do you add
what comes next?

We look at the parts of your system affected by a new store, an integration or a change in how your business works.

You receive → a map of the relationships, constraints and possible approaches with clear trade-offs.

Review architecture

Free: one audit type and one agreed area. Before we start, we agree on scope, materials and a delivery date. Fixes are discussed separately. If the evidence is insufficient, we will explain what is missing.

02 / A result you can use

A report.
Ready
to open.

One HTML file. A short summary for the decision-maker, detailed evidence for the developer. Open it offline or save it as a PDF.

  • What matters most to fix first.
  • The evidence behind the findings.
  • What already works and can stay.
  • How to verify the next step.
Open the full sample
old code /audit.html / DEMO 01

FICTIONAL EXAMPLE / ORDER ACCESS

Your orders.
Who can see them?

CUSTOMER BAPIORDER A
Issue
The server does not check order ownership.
First step
Check permissions before returning data.
Acceptance
The owner receives their order. An unauthorized user is denied access without receiving private data.

FICTIONAL DATA · NOT A CLIENT CASE STUDY

This illustrates the report format. No real project was reviewed for this example.

03 / One stage at a time

A clear stage.
Your decision.

After the audit, you decide how to use the findings and who should make the changes. The report is yours to keep.

  1. 01

    Describe
    your situation

    Tell us what the system does, where you run into difficulties and what you want to change. No source code needed to start.

  2. 02

    Agree on
    the scope

    One question, an area, materials and a delivery date. Access and code handling are discussed in advance.

  3. 03

    Receive
    your report

    Findings, evidence, review limitations and a recommended next step.

  4. 04

    Choose
    what comes next

    Your team, another developer or a small, agreed stage with Old Code.

The next stage starts
with your approval.

Before paid work starts, we agree on the outcome, price and acceptance criteria, including terms for stopping during a stage. You receive the changes and verification results.

04 / Straight answers

Before
we talk.

What the audit includes, how we handle your code and what happens afterwards.

What exactly is free?
An investigation of one agreed question in one area of the system, plus a report of the findings. We agree on materials, scope and delivery date before starting. Fixes and further investigations require a separate agreement and do not start automatically.
Do you need code access right away?
No. We start with a description of the problem, then agree on the minimum materials needed and confidentiality terms. Code access is read-only. If we need to run the system, we discuss a test environment separately. Keep passwords and customer data out of your first message.
How do you use AI?
AI may assist with analysis, but findings need verification. Before any source code is shared, we agree on which materials may be sent to which tools. If your restrictions are incompatible with our available workflow, we will tell you before the audit starts.
What if you find no issues?
The report will document the checks performed, their scope and conclusions. Finding no issue in one area does not establish that the whole system is secure. If evidence is insufficient, we will say so and explain what is needed to answer the question.
How long does an audit take?
We agree on a delivery date after defining the question and reviewing the available materials. Project size alone does not determine the timeline: scope, dependencies and the ability to verify behavior matter.
What if I choose not to continue?
The report is yours to keep. Use it with your team or share it with another developer. You are under no obligation to commission development from us. If a paid stage has already started, the agreed stopping terms apply.

05 / The first step is free

Start with
a question.

What have you wanted to understand or change about your code?

No source code needed to start.A short description is enough. Together, we will identify the area worth investigating.

You can also contact us directly:
@temrjan[email protected]

Do not include passwords, access keys or customer data.

Message on Telegram Email

A draft opens in your chosen app. You decide when to send it.