# [Your name] — what I build

[One sentence: the kind of work you want, and the strongest thing you have built.]

Read this in two minutes: each project below names the problem, what was new to me, and the proof you can click.

## The arc

Five projects in the order I built them. The point is the distance between the first and the last.

| # | Project | The problem | What was new to me | Proof |
|---|---|---|---|---|
| 1 | [Command-line app] | | | [repo] · [tests] |
| 2 | [API and database] | | | [repo] · [tests] |
| 3 | [Full-stack app] | | | [repo] · [live] |
| 4 | [Shipping pipeline] | | | [repo] · [release] |
| 5 | [Final project] | | | [repo] · [live] |

## Start here

If you only open one thing, open this.

**[Project name]** — [one line on why this one shows the most]. [Link]

## What I can do, with proof

A skill with no link is a claim. Each line points at something a reader can check.

| Skill | Where you can see it |
|---|---|
| [Language and testing] | [link to a test file or a passing run] |
| [Databases] | [link to a schema or a query] |
| [APIs] | [link to an endpoint or a contract] |
| [Front end] | [link to a running page] |
| [Automated checks and shipping] | [link to a pipeline run or a release] |

## How I work

Short. Concrete. No adjectives a reader cannot check.

- I write the test before the behavior. [Link to a commit that shows the failing test first.]
- I write down the decisions I make and what they cost. [Link to a decision record.]
- I ship in small pieces behind automated checks. [Link to a pull request.]

## What I am learning now

- [What you are working on this month, and where it will show up.]

## Contact

- [Email or profile link]

---

## About this template

This is the page that decides whether someone opens your code. It is not a list of projects. It is one story: where you started, what you can do now, and the evidence for both.

> **What this teaches:** I can present my own work the way a reader judges it. I lead with the problem and the proof instead of a list of tools.

Before you write it, ask what a reader could check in fifteen seconds. Put that first.

Fill the table left to right, one row per project, and link something clickable in every Proof cell. A row with no link is worth less than no row. Keep it to five projects. A reader is looking for the distance you travelled, not the count.

**Explain it back:** In one minute, say which project shows the most growth and why. Then name the one link you would want a reader to open first.

**Delete this whole section once you have filled the document in.** What is left should read as a finished document on its own.