Skip to content
NASHSOFTWARE SERVICES
Mike Nash
Glossary
Available for new engagements

Code review and due diligence,

in plain English

The terms used on this site and in a Confidence Report, each defined in a sentence or two. Every term links to the page that covers it in full.

Written by Mike Nash, who does the reviews himself.

The report

Confidence Report

The written report at the end of a review. It gives the call, a status for each of the eight areas, findings that each carry an action word, and an investor or board summary.

Read a sample report

Code and architecture review

An independent read of a product’s code and how it is put together, written up for the people who rely on it. It is often called a code audit.

Code and architecture review

The three calls

Every report gives one overall call: Ready, Ready after fixes, Not ready yet. There is no score, and an amber area never changes the call.

How a review works

Ready

One of the three calls. Nothing I found needs fixing first. The report says what is worth doing next, and what to leave alone.

Code and architecture review

Ready after fixes

One of the three calls. The fixes come first, and the report says what each one is and how long it takes.

Code and architecture review

Not ready yet

One of the three calls. Not safe to rely on as it stands. The report says what has to change and which parts, if any, need replacing.

Code and architecture review

Action words

Each finding in the report carries one of three action words: Fix first, Harden, Leave alone. They say what to do about it and in what order.

Code and architecture review

Fix first

An action word. Do this before anything else. It stops the product being safe to rely on.

Code and architecture review

Harden

An action word. Worth doing, but it can wait. It makes the product stronger or cheaper to run.

Code and architecture review

Leave alone

An action word. Fine as it is, or a matter of style. It does not change the call.

Code and architecture review

Depth of reading

How closely an area is read. There are three levels: read in full, sampled and light read. The report states the level for each area.

Code and architecture review

Read in full

Depth of reading: every relevant part of the area is looked at, not a selection. It is how the Production and Full reviews read most areas.

Code and architecture review

Sampled

Depth of reading: the riskiest parts of the area are read closely and the rest is spot-checked. It is how the Clarity review reads most areas.

Code and architecture review

Light read

Depth of reading: a quick pass to spot anything obvious, without digging into the detail. The report says which areas had a light read.

Code and architecture review

The eight areas

Area 1: Ownership and access

Do you hold the keys? Could a developer or agency leaving lock you out of your own product?

Code and architecture review

Area 2: Security

Could a stranger, or one of your own customers, see or change things they should not?

Code and architecture review

Area 3: Data handling and privacy

Are customer details and payments handled safely, and does everything stay correct when something fails halfway?

Code and architecture review

Area 4: Architecture and scale

Is it built on foundations that will cope as you grow, or will it start to creak at ten times the users?

Code and architecture review

Area 5: Code health

Could a new developer understand it and change it without breaking something?

Code and architecture review

Area 6: Testing and releases

When a change goes live, how do you know it works, and can you undo it if it does not?

Code and architecture review

Area 7: Hosting, monitoring and recovery

If it breaks at 2am, will anyone find out, and could you get it back from a backup?

Code and architecture review

Area 8: Delivery and key-person risk

If one person left tomorrow, would work stop? How does new work get planned and shipped?

Code and architecture review

The three reviews

Clarity

A fixed-price review, from £3,500, delivered in 5 business days. It answers the question: Is it sound enough to carry on with?

Code and architecture review

Production

A fixed-price review, from £6,500, delivered in 7 to 8 business days. It answers the question: Is it ready for users?

Code and architecture review

Full

A fixed-price review, from £9,500, delivered in 10 to 12 business days. It answers the question: Will it stand up to scrutiny?

Code and architecture review

Deals and investors

Technical due diligence

A review with a deal lens: the same read of the code and architecture, aimed at what an investor, buyer or board needs to decide. It is for a raise, a purchase or a handover.

Technical due diligence

Deal lens

The way a review is framed when money or ownership is about to change hands. It puts the findings in terms of risk and cost to the party deciding, rather than in terms of tidiness.

Technical due diligence

Investor or board summary

A short section of the report written for people who will not read the technical detail. It is indicative only, and it is not legal or investment advice.

Technical due diligence

Key-person risk

The risk that the product depends on one person, so that if they leave or are unavailable, nobody else can run or change it. The review covers it in Area 8.

Code and architecture review

Access and data

Staging copy

A test version of the product that real customers do not use. A review is best run on a staging copy with made-up data, so no customer records are involved.

How a review works

Read-only access

Permission to look at code or systems without being able to change them. It is the access a review asks for.

How a review works

A term missing, or something unclear?

Ask by email or on a call and I will explain it in plain words.