Working Surfaceissues
16 issues · since 16 September 2026

One note a day, written by the morning job from the pieces it verified, and kept here as written. Each note's links have their own pages.

Issue · 3 linksThursday 1 October 2026Three pieces from the past four days place the risk of AI-assisted work at the moment a person must explain or judge what an AI agent produced. An engineering leader, a usability researcher and a summit of product leaders each argue that understanding and judgement do not grow with output and have to be checked on purpose.
Issue · 3 linksWednesday 30 September 2026Dropbox, Shopify and Figma describe what changes once AI agents make building cheap. Dropbox checks agent changes like a person's, Shopify rebuilds its apps natively with one shared test suite, and Figma's product lead says choosing a direction is now the hard part.
Issue · 11 linksTuesday 29 September 2026When AI tools do more of the drafting and building, some work that people did along the way stops happening. Six pieces name parts of it, from practising a skill to writing down why a rule exists, and suggest how a team can keep doing that work. Five engineering pieces from 29 September cover teams of coding agents, architecture, a developer survey, earlier approvals and how junior engineers build judgement.
Issue · 10 linksMonday 28 September 2026Five pieces from designers and engineers show which jobs people keep when AI agents do the building. They keep the design system and the first screen, the review of what agents make, the files agents read, and responsibility for the product as a whole. Five engineering pieces from 28 September cover reviewing AI-written code, agents that change live systems, agents that build agents, new AI models and tests written first.
Issue · 5 linksSunday 27 September 2026When AI writes part of a team's work, reviewers and users need to see what was made, by whom and from what. The pieces label sections by author, link summaries to sources, keep one document per feature, show users when a save happens, and ask for expert reviewers.
Issue · 7 linksSaturday 26 September 2026Six pieces describe how teams change their work once AI agents can finish whole tasks. They show the result before the tool, take workflows apart before automating them, set checks before release and make people responsible for managing agents. One engineering piece from the same day asks whether engineers still enjoy the work once their team codes with AI.
Issue · 5 linksFriday 25 September 2026Three pieces look at what shapes AI work before anyone chooses: the defaults a product ships, the options a team rejects, and the material an AI can reach. Each argues that these inputs should be kept in view, and one argues that each needs a named owner. Two engineering pieces from the same day look at how AI tools change an engineering manager's job and how a large embedded-software company plans to reorganise around AI agents.
Issue · 4 linksThursday 24 September 2026Four pieces from Anthropic, Stripe, Cursor and Evil Martians describe setting the rules for AI agents' work before the work starts. The rules go into automatic checks, review policies, monitoring plans and the components themselves, and people judge what falls outside them.
Issue · 4 linksWednesday 23 September 2026Four pieces argue that people can keep up with work made by AI agents only when it reaches them in small pieces that have already been checked. They also say that the judgment people bring has to be built first, by reading real cases and by working beside experienced colleagues.
Issue · 4 linksTuesday 22 September 2026Four accounts from Warp, Linear and Bolt show how software teams check work now that AI agents produce it faster than people can review it. Each company moves part of the checking into written criteria, into files the agents read, or into a review split by expertise.
Issue · 5 linksMonday 21 September 2026Five pieces look at the work left for people once AI agents build quickly. It lies in reviewing agent-built changes, answering for what is handed over, and deciding what an interface promises its users.
Issue · 2 linksSunday 20 September 2026Two pieces look at the standing instructions people give AI agents before a task begins. Heavy users of one agent keep written rules, including which actions need their approval, and one engineer has his agent question him about each plan.
Issue · 3 linksSaturday 19 September 2026Three pieces show that AI now produces working prototypes, whole apps and product comparisons in minutes. Each argues that the result is worth trusting only when something is settled first or can be checked: a written problem, fixed parts, or values with a source.
Issue · 3 linksFriday 18 September 2026Three pieces show that a person's review of an AI agent's work is only as good as the reference that person checks against. Without a reliable reference, a reviewer can add errors instead of catching them.
Issue · 4 linksThursday 17 September 2026Four pieces show that when AI agents do the building, people's judgment moves to either end of the work. People state the problem and write checks before the build, and review the running result before it reaches production.
Issue · 5 linksWednesday 16 September 2026Five pieces show that when AI helps produce work, a person still has to check it against a source before others rely on it. Where nobody inside the company does that checking, the users end up doing it themselves.