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 display. Now let's engineer.

Compute, Organise, and Display are things you do — you trigger them, you get a result. Engineer is different. It's about building something that runs without you. You describe the rule once: when this happens, do that. Then it just works, every time, automatically.

The tasks are the same ones you've already learned. The difference is the trigger. Instead of you deciding when to run them, something else does — a new file appearing, a time of day, a folder reaching a certain state. You stop doing the work. The system does it.


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 ✓ done
E Engineer — create pipelines, automations, and repeatable workflows ← you're here
R Reason — analysis, synthesis, evaluation, research

E — Engineer

Before AI, building an automation meant writing code — a script, a cron job, a webhook, a pipeline. It was work for engineers. The idea was always simple; the implementation was the barrier.

  • A new document lands in your project folder — Majk reads it and updates the running project status automatically
  • Every Sunday morning, your Downloads folder gets organised and you get a summary of what moved
  • A new bank statement appears — the subscription tracker runs, the dashboard regenerates, anything new gets flagged
  • End of each week, a status report is generated from everything that happened and saved as a shareable page

You stop doing the work. You build the thing that does the work. That's what it means to engineer with AI.

The first pattern is the simplest: a folder that watches itself. Every new file that lands triggers the same operation. You describe the rule once — Majk keeps applying it.


What's next

The Living Document pattern: a project folder that maintains its own status. Drop in any new file — an email, a meeting note, a report — and the project status updates itself.

← Back Next →