“Prompts are dead. No wait, loops are dead. No wait.”
Desk sweep, Aug 19. The loop-and-graph churn plus the SMB agent sell.
The first obituary dropped in June. A developer posted that prompting is over, that you should be building loops that prompt the machine for you, and the post went everywhere. The engineer behind Claude Code said the same thing on stage the same week. A Google engineering lead gave the movement a name, loop engineering. By late June the obituaries were literal. An actual headline: "Prompt Engineering Is Dead. Long Live Loop Engineering." The killer barely outlived the victim. By late July the same feed turned on loops. "Loop Engineering Is Dead. Enter Graph Engineering" ran within hours of the original poster asking if everyone had moved on yet. And here's the detail the course sellers skipped: both posts were jokes. The guy who started it was mocking how fast the feed renames things. The feed took the bit literally and produced courses, roadmaps, and tool stacks on graph engineering by Sunday. By early August the coverage admitted, in writing, that nobody won and the whole fight had been swallowed by vendor content marketing. "Loop Engineer" is already a bootcamp module title. Do the math against the funeral dates. Three funerals in ten weeks. No bodies. Now the part the obituaries buried. The corpse is alive, and they knew it. Read any of the summer's explainers past the headline and prompt engineering gets quietly reinstated around paragraph nine, demoted to "a component inside the loop." The headline killed it. The fine print kept it. Then the feed changed the subject to graphs before anyone noticed the resurrection. We're calling it Headline Whiplash. That's when the skill you're told to learn on Monday dies in Tuesday's news cycle, and the thing that killed it dies the Tuesday after. And here's who this soap opera was never about: you. The entire fight was coding-agent developers arguing about tools that write software overnight. If you run a shop or a crew, nothing in your stack changed this summer. You just caught the shrapnel in your feed. Don't take our word for it. Zapier, n8n, and the rest of the automation aisle are the platforms selling you the agent story right now, so we checked their own users' words. We pulled the read pool on the connector aisle, the tools where "agents" actually touch a small business. The witnesses never mention the drama. The word barely appears. What fills the pool is the least sensational story in tech: things breaking and bills growing, the only two subjects where complaints beat praise. One read, verbatim: "Zapier agent is not great in my experience." One question, free, worth more than every course the funeral crowd is selling. Does your AI bill a flat monthly seat, or by the task and the token? Flat seat: a runaway is the vendor's problem. Carry on. Metered: a runaway is your problem, and it bills while it fails. Set the cap today, before anything runs unwatched. Alerts are autopsies. Caps are brakes. And keep the prompts. The people declaring them dead were never talking to you.