Switch into tech

Stage 5 · Lesson 7 of 7

Turning a project into a case study

Proof without a CS degree

A is a one-page account of a project. It covers the problem, who it was for, and what you built. It explains two or three key decisions and their (what you gained and what you gave up).

It ends with the result and what you would change next. Reviewers skim code, but they read a clear story, and who communicate well stand out here. Put a screenshot near the top, link the code and the , and include one honest limitation. The case study feeds your and your conversations in the next two stages.

Common trapdescribing the technologies you used at length and never saying what problem you solved or for whom.

A question to check yourself, an AI practice session and 1 cheat sheet entry come when you add the roadmap to your account. Add it

Resources for this stage

Start with

Practise

  • A guided first pull request, so your first real contribution is not your first time using Git

  • Beginner-friendly issues in active projects once you have done a practice pull request

Keep handy

  • Public datasets from many industries, often including the field you came from

  • A free developer blog for your write-ups and case studies

Also worth your time

  • The short essay behind learning in public, and why it keeps paying off

Mark this stage as not done?