Carl Frey's recent NYT piece argues that AI's real impact isn't job replacement — it's labor transfer from worker to consumer. We become our own travel agent, accountant, exterminator, doctor. The work doesn't disappear; it moves out of the labor statistics

In 2025, four companies — Microsoft, Alphabet, Amazon, Meta — spent over $300 billion on AI data centers. The combined 2026 number is forecast at $725 billion, a 77% jump in a single year. For comparison, the entire global SaaS market in 2025 is roughly $295–370 billion depending on whose definition

Someone on r/devops just asked whether to take an AWS Cloud Support Engineer role for 18 months — trading hands-on building for "AWS internals exposure and the brand on the CV." Both replies told them not to. They're right, but for older reasons than they realize.

The first time you trim an eval because it costs too much to run, you have started letting the pricing model design your agent. The problem with token pricing for AI is not magnitude — tokens aren't expensive in aggregate, by knowledge-work standards. The problem is that the unit

A post hit the HN front page this morning titled "I'm going back to writing code by hand". It documents archiving seven months of vibe-coded work on a Kubernetes GPU TUI called k10s and rewriting from scratch. 75 points, 31 comments in the first hour. The

Anthropic asked Claude Opus 4.6 to finish a couplet. Before the model wrote the second line, it had already chosen the rhyme word. We know this because their new method — natural language autoencoders — read it directly out of the activations in the middle layers of the model. The text

A short post argued this week that reliable agents need deterministic control flow, not more prompts. The argument is correct. The line that lands hardest in the piece is the one about a programming language where statements are suggestions and functions return "Success" while hallucinating. That is the

Most AI projects fail somewhere between demo works and production ships. The gap is rarely the model. It's the absence of the controls that turn a one-shot prompt into a system you can run, audit, and iterate on without setting fire to the budget. I made the chart

A recent piece called "The Bottleneck Was Never the Code" makes the right argument at the right time. Coding agents shift the constraint from typing to coordination. Organizational context — the shared understanding of what we're building, what's load-bearing, what's vestigial — is the