The New Guild

Seventy-nine years

In 1947, three physicists at Bell Labs got a sliver of germanium to amplify a signal. Seventy-nine years later, the descendants of that device can read a contract, write the software to enforce it, and explain their reasoning. Few stretches of human history have moved that far that fast, and we are living inside this one.

Every leap like this produces a group of people who learn to work the new thing before everyone else. Cathedrals had masons. The early internet had the programmers Clive Thompson profiled in Coders, people who typed instructions and watched machines get up and obey.

This essay is about the group forming now. I call it the new guild, I count myself a member, and I think the leaders who learn to work with it will get a great deal built.

Who they are

A member of the new guild is someone who can take a problem from a conversation to working software alone, by directing AI systems. Some people call them vibe coders or agentic engineers. What defines them is range: they handle the product thinking, the design, the code, the data, and the deployment in one sitting.

Medieval guilds admitted a master on the strength of a masterpiece, a finished work judged by people who knew the craft. The new guild works the same way. Its members are credentialed by things they have shipped that other people use, and many of the best ones I meet have no computer science degree.

Most have also run something of their own, whether a startup, a consultancy, or a small product that pays them. That history shapes them. They know how to find a customer and get paid, and they are less afraid than most of life outside a large employer.

Like the masons, they carry their own tools and travel between patrons. There are few of them, and a company needs only a few.

A week at Brannock Freight

Brannock Freight and everyone in this story are invented, so the pattern is visible without pointing at any real company.

Brannock is a regional trucking company with a problem in billing. A rate table changed mid-month, forty-one hundred invoices sit in a queue to go out Friday, and nobody knows how many are wrong.

Dale Pruitt, who runs billing operations, does what the company has always done and files a request with IT. The reply is reasonable by the old standards: a requirements document, an estimate of two sprints, and a start date after the quarter closes. The invoices will go out long before then.

Marguerite Okafor, the chief operating officer, has recently brought in a builder named Tess Albrecht. On Tuesday afternoon Tess sits with Dale for two hours and watches him check invoices by hand against the contract rate sheets. By Wednesday morning she has an agent that has read all forty-one hundred.

The agent corrected three hundred and twelve invoices and logged every change with its reason. It also ranked sixty that a person should look at before anything is sent. Dale's team spends Wednesday on those sixty, and the queue goes out clean on Friday.

The same week, a working group at Brannock holds its third meeting to plan a shipment tracking page for customers. Tess reads their planning documents that evening. The next morning the group gets a link and a short note: "Here is a working version. Can we iterate on the real thing?"

They meet Thursday with the page on screen. With the group's permission, Tess records the conversation and hands the transcript to her tools. An hour later the requested changes are live, along with three alternate layouts each member can click through at their own desk.

Brannock's engineers are neither slow nor careless. Their process was built for a time when software was expensive to write, so every step protected against building the wrong thing. When building costs an afternoon, the cheapest way to learn what people want is to show them.

The guild before this one

The last guild formed in the 2010s, and it was shaped by how you got in. You earned a degree, studied for months to pass whiteboard interviews, and joined a company that placed you in a defined role: engineer, product manager, designer, analyst. I came up through that system myself.

That path produced excellent specialists and the products most of us use every day. It also domesticated them, a word I use as description and without contempt. Years of studying and waiting for permission teach a person to work inside a lane.

The new guild did not come through that gate. Its members learned by building, often alone, with a model as tutor and partner. They are used to deciding what to make, and a narrow lane feels strange to them.

Some of the strongest traditional engineers are joining. Others are holding to deep technical specialties, which remain valuable but sit further from the decisions about what gets built.

The tools keep moving

The guild's range grows every few months, because its tools do. A year ago I would not have taken on anything involving three-dimensional graphics or video. Today, working with a model, I can build a playable three-dimensional game that runs in a browser, the kind of project that called for a small studio in 2020.

This changes what a patron is getting. A traditional hire brings a set of skills that deepens slowly. A guild member who stays at the frontier brings a set that widens with each release, so the person who fixed your invoices this spring may be able to build your driver training simulator by fall.

It also explains why they spend so much time experimenting. Staying current is the apprenticeship, and for this guild it never ends.

How to be a good patron

The leaders who get the most from the guild act like the patrons who commissioned cathedrals: they choose well, open the site, and protect the work. In practice that comes down to six habits.

• Choose by the masterpiece. Ask to see things they built that other people use, and ask what each one earned or saved.
• Bring a problem with an owner. "Our invoices are wrong and Dale feels it daily" is a better brief than a ticket with requirements.
• Grant access early and specifically. Read access to the real data and a safe place to build are worth more than a month of onboarding.
• Seat them beside the person doing the work. Two hours watching Dale told Tess more than a specification could.
• Review the thing. Ask for a working version first and give your feedback on that.
• Set the boundaries yourself. Decide in advance what they may not touch and who reviews what ships, then defend everything inside those lines.

Most organizations have an immune system that treats broad access as a threat, usually for good reasons. A patron's real work is negotiating with it so the builder does not have to.

What it costs

The guild's speed has a price, and a patron should know it before commissioning anything. At Brannock, one member of the tracking group had asked to hold a design decision until her director weighed in. Tess's working version settled it overnight without meaning to, and the colleague was right to be annoyed even though the page was better.

Speed can also outrun review. An agent that corrects three hundred invoices in a night can miscorrect them just as quickly. The ranked list and Dale's sixty checks mattered as much as the fixes.

Guild members also leave when they are boxed in. People who can earn a living alone will not stay long in a role that narrows them to one lane.

Six months later

By spring, Tess is still the only builder at Brannock. Marguerite brings her a question the company had shelved years earlier, after an outside firm quoted nine months and a fee larger than Tess's annual pay: are we billing everything our contracts allow?

Tess points her agents at nine years of customer contracts, about six thousand documents, and every invoice sent against them. Ten days later Marguerite has a report. Brannock has been leaving a little over two million dollars a year uncollected, in detention fees and fuel surcharges that its contracts permit and its billing system never applied.

Each finding links to the clause and the invoices behind it, so finance can verify the work line by line. Dale's team starts billing the charges the following month.

That is the leverage a patron is commissioning. One trusted person with access can now answer questions a company had priced out of reach, and the answers pay for the commission many times over. The cathedrals took generations, and the patrons who started them are still remembered for it.