RSVP →
click it. or don't — that's kind of the point.  #reverse-ysws
scroll down

you don't have to build from nothing.

most YSWS events hand you a blank file. this one hands you someone else's codebase, and asks you to actually understand it before you write a single line of your own.

dig through an OSS repo. write up what you find — the clever parts, the messy parts, the parts you'd have done differently. then build something of your own with what you learned.

01 · pick a repo
02 · write it up (track time with Lapse)
03 · ship your own app

how deep are you willing to go?

scroll to descend through the strata — or just look, the layers hold still either way

depth 0.0m — topsoil

side-quests

themed detours if you want more direction than "go read some code"

layer 01

The Compiler Trench

Dig into how a real compiler or interpreter turns text into execution. Tiny languages count.

est. depth: 8–15 hrs
layer 02

The Database Vault

Crack open how a database stores, indexes, and queries data under the hood.

est. depth: 10–18 hrs
layer 03

The Protocol Ruins

Trace a networking protocol implementation — HTTP, WebSockets, or something weirder.

est. depth: 6–12 hrs
layer 04

The Engine Chamber

Excavate a game engine or renderer. Find out where the frames actually come from.

est. depth: 12–20 hrs
layer 05

The Bootloader Crypt

Go low. OS kernels, bootloaders, anything that runs before "hello world" makes sense.

est. depth: 15–25 hrs

suggested repos

ssg (static site gen)

Small, readable, does exactly one thing. Good first dig.

shallow

redis

In-memory data store. Clean C, small enough to actually finish reading a module.

medium

caddy

A modern reverse proxy. Great if you've fought with nginx configs before.

medium

sqlite

The database everyone uses and almost nobody has read the source of.

deep

micropython

A whole language runtime, sized for a microcontroller. Surprisingly readable.

medium

doom (id-software)

The classic. Decades of write-ups exist already — see if you can add something new.

deep

FAQ

What actually counts as a "write-up"?

A real walkthrough of the code you read — example snippets, architecture choices you noticed, places you think it's inefficient or clever. Not a summary of the README.

How do I track my time?

Use Lapse for both the exploring/reading phase and the writing phase. Screenshot or link your session when you submit.

What does "your own app" need to look like?

Something that visibly uses what you learned from the repo you studied — a feature, a pattern, or an approach carried over. It doesn't need to be huge, but it needs to connect back to your write-up.

Do I have to pick a side-quest?

No — they're there if you want a themed direction. Any OSS codebase you're genuinely curious about works.

Still not convinced?

Then honestly, we don't know what will convince you. RSVP anyway and find out.

ready to dig?

pick a repo. read it like it's ancient. build something new.

RSVP for #reverse-ysws →