About DevDeter

Most technology writing treats the technology as the story. We think the more interesting story is usually the arrangement around it: who paid for it, which law applies to it, whose job it changes, and who was in the room when the terms were agreed.

What we cover

Four beats, and a piece belongs to exactly one of them so the site stays navigable as it grows.

• AI — How machine intelligence gets built, sold and governed.
• Programming — Craft notes from building and shipping software.
• Policies — Regulation, standards, and the rules being written for technology.
• Stories — Reported pieces on how all of it lands in people's lives.

How we work

Pieces are published on the site first and go out by RSS andemail at the same moment. Nothing sits behind a wall. There are no tracking pixels in the newsletter and no third-party analytics on the site.

When we get something wrong we correct it in place and say what changed at the foot of the piece. If you spot an error, tell us — corrections are the fastest way to earn a reader.

Who publishes it

DevDeter is published by Untout. Pieces run under the publication rather than a personal byline, which means the argument has to stand on the reporting rather than on who signed it.

Use the contact form — it is the only inbox, and it reaches the editor directly. Corrections go to the same place and are the fastest way to get our attention.

Funding

DevDeter is self-funded. Nobody pays for coverage, there is no advertising, no sponsored posts and no affiliate links, and no company written about here has any financial relationship with the publication.

This matters more than usual on a beat about who pays for infrastructure. If that ever changes — reader support, a grant, anything — it will be written here first, and on the pieces it touches.