Code Without a Programmer

Tasks that used to send you to a programmer get solved in one conversation. Renaming 300 files by a rule, building a formula for a spreadsheet, pulling data from a dozen documents into one table.

You do not have to write code. You describe the task in words and get a ready set of commands with an explanation of where to paste them.

For larger tasks the big developers have dedicated tools: Codex at OpenAI, Claude Code at Anthropic. They read the project files themselves, write and edit code, run commands, and check the result. People build programs and services with them.

To work with them confidently you need to understand how an application is put together and how a database works. Those basics can be picked up as you go: the same tool will explain how your project is arranged and what each part of it does.

Where to start

Describe what you have and what should come out of it, and name the program: a spreadsheet, an email client, files in a folder. From there the service breaks the task into steps itself and tells you where to paste what you get.

Start experimenting with code only on your own personal computer and only under your personal account. Do not move work files over for this; practice on your own data.

Before running anything, ask for an explanation of what each line does, and try it on a copy of your data.

Safety rules

Do not run what you do not understand. A command whose meaning was never explained to you can delete more than intended or send data out.

Do not paste work passwords and access keys into code. If they are needed, ask IT how that is done at your company.

Do not install third-party libraries on a chat's advice without checking that they exist. Fakes are published under the names of well-known services, as the chapter "Fake Apps and Extensions" describes.

On a work computer, company rules apply. A script that touches corporate systems is cleared with IT.

What this changes at work

A repetitive manual operation stops being something to put up with. An export you have done by hand every Friday for two years turns into a script in an evening. A simple task takes less; a complicated one will need help from IT.

Conversations with IT get more concrete. Instead of "please do something," you bring a working draft and ask them to check it.