Full Write-Ups, Start to Finish
CASE STUDIES
Every project leaves a trail — decisions made, problems that didn't go as planned, fixes that worked and ones that didn't. This section is where that trail gets written down properly, from the first line of code to whatever shipped at the end. Some trails are short — a bug fixed, a lesson learned in an afternoon. Others stretch across weeks, with false starts and rewrites along the way.
Not tutorials, not marketing copy — a record of what actually happened while building something real. The kind of detail that gets left out once a project looks finished. Written close to the work, not after the fact.
Section Notes
- Covers
Real projects — architecture calls, bugs, trade-offs, and outcomes.
- Format
Long-form, chronological — problem, approach, result.
- Frequency
Published as projects reach a stopping point, not on a schedule.