You've done O. Now let's compute.

Organise was about reading a pile and deciding where things belong. Compute is different. It's about doing things that used to require a programmer — reading data out of files, transforming it, calculating across it, writing results back out. Tasks that were never hard to understand, just impossible to do without code.

Now you have a CS PhD on call. You describe the outcome in plain language — Majk writes the code, runs it, and hands you the result. The barrier was never the idea. It was the implementation.

Where you are

CODER

C Compute — extract, transform, and calculate across files and data ← you're here

O Organise — impose meaningful structure on files, folders, and data ✓ done

D Display — build dashboards, galleries, visual reports, websites

E Engineer — create pipelines, automations, and repeatable workflows

R Reason — analysis, synthesis, evaluation, research

C — Compute

Before AI, these tasks belonged to programmers. Not because they were conceptually hard — but because turning the idea into working code was a skill most people didn't have.

Read the GPS metadata out of 400 photos and rename each one with the date and location
Pull every transaction from three months of bank PDFs into a single spreadsheet
Extract all the tables from a folder of reports and combine them into one file
Calculate totals and margins across 12 months of expense exports

You always knew what you wanted. You just couldn't tell a computer how to do it. That's what's changed.

Compute requires three things: knowing what to ask for, knowing how to describe it clearly, and knowing how to correct it when the result isn't quite right. That's what the next tutorials teach.

What's next

The first Compute pattern: applying one operation across every file in a folder. No code required — just a clear description of what you want done.

← Back Next →