SMRTR ProgrammingAug 17, 2026SD Times

Why Some Companies Are Pulling Back on AI Coding

Why Some Companies Are Pulling Back on AI Coding

SMRTR summary

A line of auto-generated code that deletes a customer from a database sounds efficient, even elegant. But what it won't do is archive past invoices for legal compliance, or notify the eight downstream services that need to know the customer is gone.

That gap, between generating code and actually engineering software, is at the heart of a quiet revolt happening inside some of the world's largest tech companies, where AI coding tools are being restricted or outright banned.

These aren't Luddites. They're reacting to real risks: subtle bugs that slip past code review, security vulnerabilities, fragmented codebases, and the uncomfortable question of who's accountable when AI-written code crashes a production system.

Experts estimate we're only 20 to 40 percent of the way toward fully trustworthy autonomous software engineering.

Still, the economics of AI-assisted coding are too powerful to ignore. The likely future isn't one super-model replacing engineers, but AI operating inside tightly validated environments, with humans still holding the wheel.

SMRTR provides this summary for quick context. The original article belongs to SD Times.

Read the original article
SMRTR Programming

Get the next batch of curated stories in your inbox.

This archive is built from SMRTR newsletter stories. Subscribe for hand-picked stories without the extra noise.

Related Stories

Browse Programming
ProgrammingAug 23, 2026

Rust Glancer

Rust-analyzer's memory bloat stems from treating all 6,666 dependencies equally — a tiered, IntelliJ-style backend could fix that.