LECTURESSystem Design Skills22

System Design

Intro to Verifying What You Built

The technique of "checking for yourself" the system you built

Reach a state where you can check for yourself whether the system you had AI build really works. Even without specialized testing knowledge, internalize a verification template that lets you judge "it's OK if this works" for operations.

Intro to Verifying What You Built

─ ARTICLE COVER

System Design SkillsSystem Design

§I ─ POSITION

Where this course fits

A hands-on course linked with the "run a simple system yourself" module of Claude Code training. The final piece for the field to operate a system without relying on outsourcing.

§II ─ TAKEAWAYS

What you will learn

  1. 01

    Exhaustively surface the operational happy paths and exception paths

  2. 02

    Judge the gap between "it worked" and "it's usable in operations"

  3. 03

    Hold a procedure to complete verification entirely on your own

  4. 04

    Record the verification results and tie them to recurrence prevention

§III ─ EXCERPT

Excerpt from the course

01

"It worked" and "it's usable" are different things

Having Claude build a system and seeing a screen appear is no more than "it worked." A state usable in operations is one where the right result comes back for every anticipated input, and the behavior on error is also acceptable. Verification is the work of closing this gap.

02

The 4 lenses you should check

For a single feature, verify behavior through four lenses.

  • Happy path — does the expected result come out for the expected input?
  • Exception path — behavior when you enter blanks, invalid values, or unexpected data
  • Boundary — the extremes of volume, like 0 records / 1 record / huge data
  • Operational scenario — try it end-to-end through a day's flow of operations

03

A procedure template for verification

Hold the procedure as a template so anyone can verify at the same quality.

StepWhat you doOUTPUT
1. SurfaceEnumerate the anticipated input/operation patternsChecklist of items
2. Prepare test dataPrepare data for both happy paths and exception pathsA set of test data
3. ExecuteExecute one item at a time and record the resultExecution record
4. JudgeJudge whether it's OK or NG for operationsPass/fail list + fix list

04

Verifying together with Claude

Each step of verification is work Claude is good at. Just ask "list 10 items I should check for this feature" or "prepare 5 kinds of exception-path test data" and a first draft is made. After that, select with the field's intuition and execute.

─── Continue in the download edition ───

§∞ ─ DOWNLOAD

Get the full materials, exercises and answers
in the download edition.

─ EXERCISE

Using a simple system you actually built with Claude Code as material, experience one cycle from surfacing verification items → executing → judging → requesting fixes.

Lecture slides

Every slide of the course

Cheat sheet

Quick reference for the field

Exercises

With answers and grading

Advanced / test

Hands-on plus rubric

INCLUDED PDFS ─ 6files

IT Consulting Guidebook | A Systematic IT Consulting Method Across 18 Lessons, from IR Analysis to PM | IPLoT Inc.