Skills · Briefing

The new technical job is directing, not typing

For a long time, getting software built meant finding someone who could write it. The scarce skill was typing code. That is changing quickly, and the change affects what you should look for, what you should learn and what you should be willing to pay attention to.

What changed

A sentence can now become a working tool. A person who describes what they want clearly can get a first version in an afternoon that used to take weeks. The writing of the code has become cheap and fast.

What has not become cheap is deciding what to build, noticing when it is wrong and knowing what it will do to the rest of the business.

The job moves up a level

The work now looks like direction. Someone has to say what the thing is for, who will use it, what it must never do and how we will know it works. Then someone has to review what comes back, test it against the real world and decide whether it is good enough to rely on.

That is closer to what an editor, a site foreman or a good manager does than to what a typist does. It rewards judgment over speed.

Writing code got cheap. Deciding what to build did not.

What this means for an owner

You do not need to learn to code. You do need to get good at three things.

• Describing the problem. Say what goes wrong now, how often, what it costs and what a good outcome looks like. Vague briefs get vague results, from people and from tools.
• Judging the result. Use it with real examples, including awkward ones. If you cannot tell whether it is right, you cannot rely on it.
• Keeping the decision. The tool can propose. A person decides, and a person is accountable.

What it means for the people you hire

Be careful with anyone whose pitch is that they can build quickly. Quickly is now ordinary. Ask instead how they find out what you need, how they test, and what they do when the first version is wrong.

The people worth paying for can tell you what not to build. They notice the missing case, the edge that will bite in March, the part that will be painful to maintain. That is judgment, and it comes from having seen things go wrong.

What it means for your team

Your best people already hold the knowledge that matters: how the work really runs, where it breaks, what the customer actually means. That knowledge is now more valuable, because it is what turns a general tool into a useful one. Involve them early. People support what they helped shape, and they notice problems an outsider will not.

A practical habit

Before anything is built, write one page.

1. The job, in plain words.
2. Who does it today and how long it takes.
3. What a good result looks like, with two real examples.
4. What must never happen.
5. Who checks it and how often.

If you cannot write the page, the problem is not ready to be built. If you can, you have done the hardest part, and the build is the easy bit.

The short version

The technical work is shifting from typing to directing. Get good at saying what you want and at checking what you get. That is where the value sits now.