Chapter 18: The proof

A repo worth showing

One public project small enough to read in ten minutes, where the process is visible as well as the result: the brief, the checks, the history, and what went wrong. This is our suggestion. We found no employer saying which artefact persuades them.

Anyone can now generate a plausible app in an afternoon, so an app shows little by itself. Our reasoning is that the process around it is harder to fake, and gives an interviewer something real to ask about. Size matters too: nobody reads your big project, and you can't defend every line of it.

Say it to your agent

“Audit this repo as a sceptical senior engineer with ten minutes. In order: does the README say what this does and what isn't done, does one command run it, is there a brief, what does AGENTS.md say, what does CI block, and do the tests fail when the code is wrong? List what you can't find. Don't add anything yet.”

The workshop

Name a word, or describe what you mean in everyday language.