Developer relations after the cheat code machine

The pattern

It has been reported that educators and technical content creators are hearing the same worry: engagement is softer, course sales are softer, and people seem less willing to pay for educational material than they were a year ago. Strange, right? Software activity doesn’t look like it’s shrinking. If anything, more code is being produced than ever — “produced,” since “written” feels old-fashioned now. So why does the market for learning feel weaker?

Why courses are wobbling

Here’s the rub: many folks weren’t buying courses just to memorize APIs. They were buying a way of working — how to structure systems, how to debug, how to choose between options, how to ship in the real world. Those are survival skills for the job, not rote documentation. Enter the “cheat code machine”: an AI coding agent that scaffolds projects, generates examples, and answers prompts. It isn’t perfect, and it’s not always trustworthy, but it often gives enough plausible code to make paying for a traditional course look less attractive. If your choice is a course or more access to the machine, the math changes fast.

DevRel’s new job

So what should developer relations do? The pivot is clear: devrel can’t just be about docs and example snippets anymore. It has been reported that audiences now want to see judgment — where someone trusts the model and where they don’t, how they verify outputs, how they recover when an agent confidently wanders off. DevRel needs to help humans develop that judgment. Teach mental models. Teach auditing. Teach the rituals for spotting “plausible but cursed” outputs. That’s the layer of learning that survives contact with an actual job.

What still works

Formats that show process are holding up: coding streams, creators who reveal their playbook, walkthroughs that mix human decision-making with model delegation. People want to watch the seam work — when a person leans on the agent and when they step in. Call it calibration, call it craft. Either way, developer relations that teach people how to think about, evaluate, and coexist with these agents will be the ones that stick.

Sources: sunilpai.dev, Hacker News