Loading...
The use case

The biggest AI use case is coding.

Not coding as a career. Coding as a way to make the computer do the exact thing you need: pull the data, build the dashboard, change the workflow, create the little tool no app store was ever going to sell you.

That is why coding agents matter: they turn plain English into working software.

Once that clicks, the question gets practical fast: what can you actually do with coding? Almost everything starts with three moves — and each builds on the last:

Coding move 1

Connect your data, wherever it lives

The first thing coding lets you do is reach across the walls between your tools. Your data lives all over the place: some in email, some in your billing system, some in spreadsheets, some locked inside apps. A coding agent can write the small program that pulls that information out, cleans it up, and lays it out in one tidy place. Get the data together first, and everything you build after it gets easier. How that works, without the scary API talk →

  • Years of receipts buried in email — dug out into one organized spreadsheet
  • Files scattered across drives and folders — gathered into one place
  • Reviews sitting on five different sites — pulled into a single sheet, with the trend
Coding move 2

Make your own mini-apps

With your data in reach, coding lets you build on top of it. Think about the apps you pay for or put up with — each one is somebody else's guess at what you need, close but never quite right. Now you can describe the exact thing you want and have the agent build it. People with zero coding background are making little apps that fit their life and work, instead of signing up for another subscription.

  • A spending dashboard built straight from your bank statements
  • One screen with the five numbers you actually steer by, always current
  • A search box that answers questions from all your files — wherever they live
Coding move 3

Hand over the busywork

The last move is where coding stops looking like "making an app" and starts looking like leverage. Anything you've connected or built can be set to run on its own: every morning, every Monday at 8, or the moment a certain kind of email arrives. You say the schedule in plain English, the agent writes the machinery, and from then on the work just happens.

  • A folder that files whatever you drop into it — read, renamed, logged
  • A morning brief that's ready before you are
  • A daily check that runs so you never have to remember it
What coding can do

Real-World Examples

1 Connect

Think of the shipping receipts piling up

You ship constantly, and the proof of what each one cost is scattered everywhere — confirmation emails, PDF invoices, the carrier's website. First move: have the agent write a small program that gathers every receipt into one tidy spreadsheet — date, tracking number, weight, where it went, and what you paid. The proof that was scattered across your inbox and the carrier's site now lives in one organized place, ready to use.

2 Build

Now see what it's actually costing you

Build a report on top: what you spend by month, your cost per package, which routes and which weeks run high. And the report does the noticing for you — it flags where costs crept up, the packages you were overcharged on, the surcharges quietly adding up. You're not assembling numbers anymore; you're reading the takeaways you'd have paid someone to find.

3 Automate

Now the review runs itself

Put it on a schedule. Every month the new receipts get gathered, the report refreshes, and a short rundown of what changed — and what's worth questioning — is waiting for you. The cost review you never quite found time for just shows up, and all that's left is deciding what to do about it.

In the Field · A series

The hard part isn't believing coding matters. It's knowing what to build.

That is the whole point of this site: agentic coding is the main use case, but most people do not wake up knowing what software they should ask for. In the Field is a growing series of real accounts: one person, one real job, walking through exactly what they built with a coding agent and in what order.

CX
Field note 01 · Customer experience

A customer service manager builds their own operations system

From scattered reports to automated visibility, every conversation graded for quality, and outreach that improves itself — built piece by piece, no code written by hand.

Gladly Claude Code

See the whole series — In the Field →