Five judgement exercises in the language of your choice — nothing to build, everything to reason about.
An engineering-principles template by RedDuck. Fork it, work through the tasks in the language of your choice, push your work. The tasks are about spotting a flaw, naming it, and arguing the fix; the work is reviewed by reading the files you push, so nothing needs to build or run.
| Area | Technology |
|---|---|
| Languages | TypeScript, Python, Java, C# — pick one and use it throughout |
| Task format | TASK.md brief + SOLUTION.md you fill in |
| Coding tasks | A starter file per language in src/; task 05 also ships tests/ |
| Tooling | None — no build step, no dependencies, no runner |
flowchart LR
A[TASK.md brief] --> B{Coding task?}
B -->|yes| C["src/ starter in your language"]
B -->|no| D[SOLUTION.md]
C --> D
D --> E[Push to your fork]
Each task is a folder with a TASK.md brief and a SOLUTION.md you fill in. Coding tasks also have a src/ folder with a starter file in each supported language. Complete the starter for your language and leave the other languages as they are.
.
└── 01-common-sense-check/
├── TASK.md # brief — read this first
├── SOLUTION.md # your write-up
└── src/ # starter per language
├── checkout.ts
├── checkout.py
├── Checkout.java
└── Checkout.cs
| # | Task | What you do | Code |
|---|---|---|---|
| 01 | 01-common-sense-check |
Find and fix a common-sense flaw | src/ |
| 02 | 02-recognize-bypass |
Recognize when a bypass is available | write-up only |
| 03 | 03-core-periphery |
Apply core and periphery | src/ |
| 04 | 04-content-derived-factory |
Build a content-derived factory | src/ |
| 05 | 05-adversarial |
Break the system as an adversary | src/ + tests/ |
No install, no build. Clone your fork, open 01-common-sense-check/TASK.md, and start reading.
- Read the task's
TASK.md. - For a coding task, complete the starter file for your language in
src/. - Write your answer in
SOLUTION.md. - Commit and push to your fork.