pllu.net

MIT Sloan and Stanford researchers had 1,000 adults ask chatbots for financial guidance, then simulated lifetimes of following it. The advice was better than the researchers expected: higher savings, diversification, sensible risk reduction with age. The catch is that outcomes tracked prompt quality. Women and less financially literate users ended up roughly $50,000 worse off by 60, and people unfamiliar with AI nearly $100,000 worse, because their prompts drew weaker advice. The models also leaned on rules of thumb, failing to adjust to shocks like unemployment.

Good advice being freely available but unevenly extractable is a striking new kind of inequality.

Sean Goedecke argues that fully understanding your codebase is a small-team luxury. In large systems nobody understands it all, and effective engineers work from partly correct theories, making educated guesses and dealing with the consequences. He frames “pure” engineering (small codebases, complete understanding) and “impure” engineering (large systems, partial models) as different professional cultures, and treats understanding as one value to trade off among many, like performance or compliance.

A useful counterweight to cognitive debt: if full cognitive coverage was never on offer at scale, agents are not taking away something we actually had. Uncle Bob’s gauntlet of constraints is one way of living with that.

Manifest ran an LLM router for four months, classifying requests into complexity tiers and routing them across providers to cut costs, then killed it. A prompt alone does not reveal how hard a task is, prompt caching (cache reads 75 to 90 per cent cheaper) undercuts the savings, and switching models mid-workflow hurts consistency. Their conclusion: a good router stays sticky to one model, doing its job “by, ironically, not doing it”.

The HN thread broadly agrees that frontier models are now interchangeably good for everyday work, and that nobody has time to learn each model’s quirks when a new one lands every week. The consistency point rhymes with cognitive coverage: switching tools constantly means never really knowing them.

Y Combinator’s software team has open-sourced qm, an agent platform for a whole company rather than one person, living in Slack and on the web. A headless TypeScript core with Postgres handles identity, dual-scoped memory and permissions (personal workspaces plus shared team projects), sandboxed tool execution, and crons for background automation. The harness itself is pluggable: Claude Code, Codex, OpenCode or Pi. MIT-licensed and designed to be forked privately rather than consumed as a product.

A production-scale data point for the ideas in anatomy of an agent harness and harness engineering.

Uncle Bob Martin (coding since the late 60s) no longer reads the code his agents write. Instead he surrounds them with extreme constraints, from unit and gherkin tests to mutation testing, and trusts code that has “run the gauntlet of all of my constraints and tests”.

The polar opposite of cognitive coverage: commit at zero understanding and bet the harness makes up for it. Harness engineering and Jason Swett’s TDD skill, taken to the logical end.

A browsable queue of Wikipedia rabbit holes and evergreen YouTube videos that have been popular on Hacker News.

Satya Nadella used the term “cognitive coverage” on Hard Fork to describe how much of the code a developer understands when they commit it. Basically the flip side of cognitive debt, with a nice parallel to test coverage.

Jason Swett argues that agents only write useful tests if they are given a concrete process to follow. Models may know about TDD in the abstract, but they default to vague, performative, or overcomplicated tests.

Basing the agent loop on “specify, encode, fulfil” gives the agent an executable target, keeps speculative implementation (code/feature bloat) in check, and makes refactoring easier to review.

John Smart’s Transcension Hypothesis proposes that advanced entities or civilisations may not expand outward across the standard universe indefinitely. Instead, they may transcend our observable frame by moving inward toward denser, more computationally efficient, or more information-rich domains.

David Oks argues that AI job loss will be slower and less sudden than the current panic suggests. His case is that humans and AI will stay useful together for a long time, because real work has bottlenecks, demand grows when things get cheaper, and society adapts more slowly than models improve.

Computers required complementary investments that took years or decades to develop: new business processes, organisational restructuring, worker retraining, new management practices. It took until the 90s to see any macroeconomic productivity impact

Annie Vella on a Thoughtworks retreat about the future of AI-driven software development. People are starting to name the questions around cognitive load, trust, platform foundations, agent governance, and the changing shape of engineering work. The key lesson for her was “Nobody has this figured out”