Majk Majk ·
1. Welcome 2. Organise Your Downloads 3. The CODER Framework 4. CODER — The Moves 5. O — Organise 6. Interpretive Organisation 7. C — Compute Overview 8. Batch Operation 9. Map / Reduce 10. D — Display Overview ✓ 11. Corpus to Dashboard 12. E — Engineer Overview 13. Living Document 14. R — Reason Overview 15. Tradeoff Analysis 16. Generate Failure Scenarios 17. The Cross-Reference 18. The Stress Test 19. Course Complete 20. Scenario Catalog 21. Resume Screening 22. Performance Review Draft

You've learned to compute. Now let's display.

Compute was about reading data out of files, transforming it, calculating across it. Display is different. It's about taking everything you've gathered — bills, notes, feedback, numbers, documents — and turning it into something a person can actually look at and understand.

Not a table in a terminal. Not a CSV. A real, designed artifact — a dashboard, an infographic, a visual report — that you could send to someone and they'd immediately get it. The kind of output that used to require a designer and a developer. Now it just requires a clear description of what you want.


Where you are

CODER

C Compute — extract, transform, and calculate across files and data ✓ done
O Organise — impose meaningful structure on files, folders, and data ✓ done
D Display — build dashboards, galleries, visual reports, websites ← you're here
E Engineer — create pipelines, automations, and repeatable workflows
R Reason — analysis, synthesis, evaluation, research

D — Display

Before AI, turning raw data into a designed visual output meant at least two people: someone who understood the data and someone who could build the thing. The gap between "I know what this data means" and "I have something I can show people" was real work.

  • Turn 18 months of credit card statements into a financial dashboard — charts, categories, trends, subscriptions — as a single HTML page
  • Take a folder of quarterly notes and project docs and produce a polished one-pager that makes your work look as good as it is
  • Convert a set of survey responses into a shareable visual summary — themes, quotes, what's changing
  • Build a personal reading library page from your highlights and notes — cards, quotes, themes across books

The output is always something you could open in a browser, send to someone, or drop into a presentation. One file. No setup required.

What you describe determines what you get. The more precisely you can say what the output should look like — what sections it has, what it should feel like to read, what someone should walk away knowing — the better the result.


What's next

The first Display pattern: take a corpus of files — bills, notes, documents — read across all of them, and render everything into one polished dashboard a person can actually use.

← Back Next →