Projects
MADE HERE, DEFENDED HERE
Everything built at Apex goes through the same gauntlet. It is slower than shipping a tutorial project, and it is the reason the work holds up.
WHAT A PROJECT HAS TO SURVIVE
- 01
A brief with a standard attached
Every piece of work says what a finished version must show. Not a topic — a bar.
- 02
Built with other people
Most work is done in a group of four or five, and the record shows who actually contributed.
- 03
Read by a person
A mentor goes through it and says what is missing. Nothing is graded by a script.
- 04
Defended out loud
You explain the architecture to people who will ask why you chose it. Weekly.
- 05
Rebuilt when it needs to be
Revision is the normal case, not a punishment. Most things go round twice.
- 06
Signed off, or not
A mentor puts their name to it. That signature is what you leave with.
The long version
HOW THINGS ACTUALLY GOT MADE
Write-ups appear here as members publish them — each one is the story of a real project, written by the person who built it, from the record of how it actually came together.
The work is meant to be useful to somebody other than the person who made it. A tool, a library, documentation, a piece of research — not a portfolio piece that proves you are clever.