AI Slop

Low-quality, homogenized, telltale AI-generated output that nobody owns or understands — recognizable by style markers and costly to information ecosystems.

Also known as: AI slop, ai slop, slop, AI workslop, workslop, blurple slop, AI-generated document / slop, tells, digital smell

How authors use it

Oldest first (extraction date when no publication date is known).

Documents (29)

• TBM 439: Day At The Gig... John Cutler from The Beautiful Mess · 2026-09-11 Reader 🖥️
  AI can accelerate the mechanical formalization of sensemaking artifacts a person has already understood, but it cannot solve the harder problem underneath — telling which of an organization's proliferating artifacts still reflect current reality — so genuine organizational context remains something you have to actively create through your own exploration and other people's tacit knowledge, not something AI can spoon-feed you.
• When Content Is Free, Trust Is the Product Julie Baron · 2026-09-10 source ↗ Reader 🖥️
  As the cost of producing content collapses to zero, the scarce, valuable thing becomes trust — a reciprocal network of vouching among authors, publishers, and practitioners, earned and re-earned continuously — and that trust matters for AI systems consuming and generating technical knowledge just as much as it does for human readers.
• Are You Getting Your Money's Worth from AI? James Shore · 2026-09-08 Reader 🖥️
  Because AI's costs and benefits in software development are real, substantial, and easily misjudged by anecdote, self-assessment, or gut feel, organizations facing consequential tradeoffs between speed, cost, and people's jobs must rigorously measure both sides — using durable, outcome-anchored, approach-level metrics rather than gameable activity proxies like lines of code, pull-request count, or individual performance targets.
• How to turn your AI into a world-class designer Anshu Chimala · 2026-09-01 Reader 🖥️
  AI models default to bland, repetitive ('design-by-committee') design because their training rewards the statistically safest choice at every token, so producing distinctive AI-generated design requires deliberately counteracting that bias at each stage of a Discover/Define/Deliver process — injecting externally-sourced variety and ambition, judging output with a fresh-context critic instead of the generating agent, enriching it with image/video generation, and then subtracting rather than adding to reach a polished result.
• Andrew Kelley Interview: Why He Built Zig, Banned AI Contributions, and Moved Zig off GitHub Bruno Couriol · 2026-09 Reader 🖥️
  Because AI-generated open-source contributions are reliably low-quality and net-negative once maintainer review time is counted, and because code review is really an investment in cultivating future human core contributors rather than a pure quality filter, healthy open-source governance requires categorically banning AI-assisted contributions and preferring infrastructure (Codeberg over GitHub) whose institutional incentives favor long-term stability over corporate growth pressure.
• The Hidden Realities of AI Adoption Kate Niederhoffer (BetterUp Labs) and Thomas H. Davenport (Babson College), hosted by Tom Stackpole (HBR) · 2026-07-30 Reader 🖥️
  AI adoption succeeds or fails in an organization's invisible layer — the workflows, trust, and knowledge-validation practices surrounding the technology, not the technology itself — so leaders must treat augmentation as a deliberately governed, segmented, and measured redesign of work (tracking trust as a leading indicator and closing human-verification gaps in automated chains), because leaving that layer ungoverned decouples effort from quality ("workslop"), erodes trust in inter-organizational processes ("knowledge decay"), and hollows out the human judgment the whole system depends on.
• Presentation: Getting Rid of LeetCode Interviews in the World of AI Daniel Doubrovkine · 2026-07-29 source ↗ Reader 🖥️
  Because algorithmic whiteboard interviews measure luck and recent rehearsal rather than genuine engineering ability — as the speaker's own repeatedly inconsistent interview record proves — companies should replace them with open-ended, AI-assisted system-design exercises that reveal the judgment and human skills AI cannot substitute.
• Stranded in the Slow Zone Tim O'Reilly · 2026-07-24 source ↗ Reader 🖥️
  Frontier AI agents now let individual builders create personal systems with the complexity and fragility of enterprise software, so the DevOps discipline that once belonged only to large organizations — documentation that outlives any one model, and tool portability rather than model-agnostic architecture or self-hosting — has become a personal survival skill, even as the same shift turns engineers into managers of AI 'bots' and raises the same craft-versus-slop question for writing that it already raised for code.
• You Probably Won’t Read This Article…and That’s OK Rufus Rock · 2026-07-23 source ↗ Reader 🖥️
  The collapse in the cost of producing credible-looking work — papers, code, bug reports, blog posts — across every domain is the latest instance of a recurring historical pattern in which cheap production overwhelms a scarcity-based trust signal and forces a new socio-institutional gate to be invented, but for AI specifically neither leaning on existing human-centric gatekeeping institutions (which entrenches incumbents) nor building an AI-based gatekeeper (which inherits the same blind spots and incentive problems as what it gates) is a clean solution.
• Fragments: July 21 Martin Fowler · 2026-07-21 source ↗ Reader 🖥️
  This is not a single-thesis essay but a set of retreat dispatches with no forced unifying claim; the headline findings from the underlying Thoughtworks report are quoted up front but only two of the five (the executive/engineer expectation gap, and — more thinly — verification-as-bottleneck) are actually elaborated in the body, while the recurring thread that does run through the fragments that follow is a practitioner's-eye skepticism about the gap between AI hype and what people who actually work with LLMs observe — in board expectations, incident response, vibe-coding governance, and even the felt experience of reading AI-touched prose.
• A cautionary tale about AI in tech writing: Why "Trust but Verify" is the only way to scale Betsalel (Saul) Williamson · 2026-07-13 Reader 🖥️
  The genuinely scalable use of AI in technical documentation is not to trust the LLM's raw output but to wrap it in a software-development-style pipeline -- specs as ground truth, deterministic tools (linters, formatters, style checkers) doing everything mechanical, and human 'trust but verify' review concentrated only on the residual, non-automatable judgment work (procedure validity, UX intent, omission, accountability) -- so that the 8-hour/17,500-word claim is evidence not that AI collapses the verification burden of technical writing but that a disciplined pipeline can relocate and compress it enough to make speed and rigor compatible.
• Adam Mosseri: AI is a tailwind for authenticity Adam Mosseri (guest); Lenny Rachitsky (host) · 2026-07-11 Reader 🖥️
  Because AI makes creation nearly free and floods the world with synthetic content, the scarce and durable human advantages become taste, judgment and authenticity — which Mosseri argues is a tailwind rather than a headwind for Instagram (audiences will seek out real people and creators, not less), and which in turn reshapes how work is organized: teams compress into small generalist 'pods' led by a new 'product staff' role, while hiring rewards curiosity, grit and a willingness to try over deep specialization.
• Who cleans up after the vibe-coding party? Sam Learner · 2026-07-11 Reader 🖥️
  AI coding tools have made producing an open-source contribution nearly free while leaving the cost of reviewing, verifying and maintaining it entirely on human maintainers -- degrading the reputational and communal incentives that sustained volunteer contribution and pushing individual maintainers toward uncoordinated, defensive responses (ending bug bounties, banning AI submissions outright) in the absence of any systemic rebalancing of who does software's unglamorous, chronically undervalued maintenance work.
• Should You Still Become a Software Engineer in 2026? GitHub VP Jean Lee (interviewer); Scott Hanselman (guest, VP & Member of Technical Staff, Microsoft/GitHub) · 2026-06-25 source ↗ Reader 🖥️
  AI coding agents are the latest in a recurring cycle of developer 'power tools' that change the tools but not the craft or its human accountability, so the real risk of the AI era is not that engineers become obsolete but that the profession fails to deliberately re-engineer its junior-to-senior training pipeline (via something like nursing's preceptor model) before AI hollows out the tasks juniors traditionally learned on.
• The best response to AI slop, infinite advice, and online noise is from Robin Williams Jay Acunzo · 2026-06-18 source ↗ Reader 🖥️
  AI slop, infinite online advice and content noise are all the same thing — secondhand information, knowing *about* — whereas the durable, non-commoditizable value of any creator's work comes only from firsthand lived experience synthesized through a distinctive personal perspective, so the response to the AI era is to draw on your own life rather than let the noise convince you your experience doesn't matter.
• We don't write code anymore Vincent Quigley · 2026-06-12 source ↗ Reader 🖥️
  Software engineering has entered a fourth generation of abstraction in which implementation is cheap and the hardest, most valuable work has moved up a level to framing, specifying, steering, and reviewing — which requires engineers, teams, and engineering management itself to reorganize around judgment and review capacity rather than code production.
• Flood of AI 'garbage' is pushing open-source developers to the limit New Scientist - Home · 2026-06-05 source ↗ Reader 🖥️
  AI tools have made producing open-source code contributions nearly free while the human cost of reviewing, fixing and rejecting them has stayed fixed or risen, and this asymmetry is driving burnout, maintainer attrition, and defensive lockdowns across open-source projects that nearly all software depends on.
• How People Are Really Using AI in 2026 Harvard Business Review · 2026-06-01 Reader 🖥️
  Across a third annual edition, generative-AI use is widening into an ever-broader and more intimate range of tasks — best read as shifts in emphasis, not ruptures — with people increasingly outsourcing both their thinking ('thinkslop') and their emotional lives to AI, even as, in business, the technology so far yields mostly marginal efficiencies rather than game-changing transformation, leaving the survival of human agency as the open question.
• What we lose when AI writes for us Afonso Franco · 2026-05-25 Reader 🖥️
  When we let AI write for us, we don't merely outsource a technical task — we outsource the cognitive struggle through which we clarify beliefs, form judgment, and constitute the self, and at civilizational scale this risks converging humanity not just on a shared style but on shared thought.
• Using AI to write better code more slowly Nolan Lawson (Read the Tea Leaves) · 2026-05-25 source ↗ Reader 🖥️
  LLMs are flexible enough to produce either fast, unvetted slop or slower, carefully reviewed and understood code, and deliberately choosing the latter — running multiple different models to hunt for bugs, personally validating and triaging what they find, and refusing to ship a PR you don't fully understand — is a better way to use AI for programming, even without a velocity payoff.
• 17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-05-18 source ↗ Reader 🖥️
  Large sociotechnical transformations — whether NAV's digital transformation a decade ago or the current AI shift — work by accumulating slow flywheel momentum that then snaps into a sudden S-curve climb through a high-friction liminal phase, and the leaders who guide organizations through such transitions are those who can 'take the elevator' across organizational floors and disciplines, translating between domain, technology and executive language while staying close enough to the craft that their advice is grounded in something real.
• This week on How I AI: The internal AI tool that's transforming how Stripe designs products (Protodash at Stripe) Lenny's Newsletter / Owen Williams · 2026-05-09 Reader 🖥️
  Internal AI prototyping tools that embed a company's own design system produce dramatically higher-fidelity results than generic AI tools, and when made accessible to non-engineers (designers, PMs), they shift organizational culture from document-based proposals to working demos — enabling faster exploration, better cross-functional communication, and more-informed design decisions.
• The growing AI backlash Gary Marcus · 2026-05-04 source ↗ Reader 🖥️
  Generative AI has been a net negative for society outside a few domains like coding, the backlash was predictable and is now accelerating toward political salience, and the industry bears primary responsibility for privatizing gains while externalizing harms.
• Eating My Own Dog Food: How I Used the Framework to Write the Post About the Framework Marc Millstone · 2026-05 source ↗ Reader 🖥️
  The same risk-and-differentiation framework that tells engineering teams where to grant AI autonomy also governs knowledge work like writing: delegate heavily where errors are cheap and recoverable, retain full ownership where the work carries the argument's credibility, and use AI as an adversarial critic rather than a ghostwriter.
• Managers Are Struggling to Keep Up with the AI Productivity Boom Mollie West Duffy (with Liz at Atlassian) · 2026-05 Reader 🖥️
  As AI accelerates individual execution, managers become the new bottleneck; their role must shift from editor-in-chief (policing the work) to strategic guide (clearing the path) via five behavioral changes — focus on where not what, make managing up a core skill, deploy AI as an EQ coach, use AI to filter rather than flatten, and restructure check-in cadence.
• The AI paradox: More automation, more humans, more work | Dan Shipper Lenny Rachitsky (host); Dan Shipper (guest, CEO Every) · 2026-05 Reader 🖥️
  Despite radically improving model capabilities, the agentic era will paradoxically generate more work for more humans — because every agent needs a human gardener, SaaS persists (with users bringing their own tokens via Codex/Claude Code), and progress merely commoditizes yesterday's competence and pushes humans further up the value chain to define what is worth doing next.
• DeepSeek v4, and the end of the OpenAI/Microsoft AGI clause Simon Willison · 2026-04-30 Reader 🖥️
  A snapshot of late-April 2026 in AI: a Chinese open-weights lab is now pricing the frontier into the floor, the AGI clause that supposedly governed the OpenAI/Microsoft relationship has been quietly written out of existence, and Willison's own LLM tooling has to be rebuilt around the assumption that model output is no longer just text — together describing an industry where the economics, the legal scaffolding, and the developer abstractions are all reorganizing around the same new reality of multi-modal, agentic, commoditized models.
• Harness design for long-running application development anthropic.com · 2026-03-24 Reader 🖥️
  Harness design for long-running autonomous coding should be approached as a moving target: build a multi-agent architecture (planner, generator, evaluator) that compensates for the current model's specific weaknesses on long-horizon, subjective-judgment tasks, then aggressively strip components as model capability advances — because every harness component encodes an assumption about what the model can't do alone, and those assumptions go stale.
• No Vibes Allowed: Solving Hard Problems in Complex Codebases – Dex Horthy, HumanLayer AI Engineer · 2025-12-02 source ↗ Reader 🖥️
  Solving hard problems in large, brownfield codebases with coding agents requires treating the context window itself as the scarce, team-visible resource to be engineered — through a research/plan/implement workflow with deliberate, frequent compaction — rather than either unreviewed 'vibes' or an over-literal, semantically diffused 'spec-driven development'; and the harder, still-unsolved problem is adapting team workflow, review practice, and culture to a world where most shipped code is AI-authored, not improving the agent tooling itself.

Propositions touching this concept (20)

By publication month, oldest first (extraction month when no publication date is known).

2025-12

• explicitStatic, wholesale onboarding documentation for agents should be rejected in favor of progressively sharded, on-demand context (root-level repo context, then sub-directory context pulled in only as needed), because a single large upfront document consumes the smart zone before work starts, and because teams will not reliably sustain the ongoing effort required to keep a static document synchronized with a changing codebase — it will instead drift into stale falsehoods ('slop').
  No Vibes Allowed: Solving Hard Problems in Complex Codebases – Dex Horthy, HumanLayer · p11
• explicitdevelopedCoding-agent capability itself is expected to commoditize; the harder, differentiating problem for organizations is adapting team workflow, SDLC, and culture to a world where the large majority of shipped code is AI-authored — and that adaptation must be driven top-down by technical leadership, because it is otherwise producing a growing rift where senior engineers increasingly resent the cleanup burden from AI-generated 'slop' shipped by less experienced colleagues.
  No Vibes Allowed: Solving Hard Problems in Complex Codebases – Dex Horthy, HumanLayer · p13

2026-02

• explicitFull agent autonomy introduces its own entropy problem: Codex replicates existing patterns in the repository, including suboptimal ones, so quality drifts over time; the team's initial manual response — one engineer-day per week ('20% of the week') spent removing 'AI slop' — did not scale.
  Harness engineering: leveraging Codex in an agent-first world · p13

2026-04

• explicitAI models have crossed a qualitative threshold in vulnerability research, shifting from generating 'AI slop' reports to finding real, high-severity bugs
  Meta's new model is Muse Spark, and meta.ai chat has interesting new tools · p4

2026-05

• explicitdeveloped54% of managers report receiving AI workslop (BetterUp)
  Managers Are Struggling to Keep Up with the AI Productivity Boom · p3
• explicitcorroboratedAI summaries are functionally useless because they flatten signal and slop indistinguishably
  Managers Are Struggling to Keep Up with the AI Productivity Boom · p8
• explicitLLMs are flexible enough to be used just as effectively to write high-quality code slowly as to write low-quality code fast — 'slop' is a choice of use, not an inherent property of the tool.
  Using AI to write better code more slowly · p1
• explicitReading AI-written documents in good faith requires senders to be able to defend each line; otherwise the document is a social violation ('slop').
  The AI paradox: More automation, more humans, more work | Dan Shipper · p22
• explicitcontestedGeneric AI design/prototyping tools produce low-quality output ('blurple slop') because they lack knowledge of company-specific design systems.
  This week on How I AI: The internal AI tool that's transforming how Stripe designs products (Protodash at Stripe) · p1
• explicitcorroboratedGenAI is undermining education, enabling mass surveillance, increasing disinformation, deepfake porn, bias, cybercrime, and economic disparity, while drowning the world in slop and environmentally damaging data centers.
  The growing AI backlash · p2

2026-06

• explicitAI slop, online noise, and infinite advice content are not three problems but one — all are secondhand information (knowing *about*), categorically distinct from firsthand lived experience.
  The best response to AI slop, infinite advice, and online noise is from Robin Williams · p1
• implicitThe essay exempts its own distinctive-voice secondhand advice — and its use of a fictional, transcribed movie scene — from the 'secondhand slop' it condemns, silently reclassifying secondhand material transmitted through a distinctive personal perspective as firsthand and valuable.
  The best response to AI slop, infinite advice, and online noise is from Robin Williams · p10
• implicitIn an AI-saturated discourse, the credibility of security warnings is itself fragile: much of the thread dismissed a substantively real warning as 'AI slop', while others delegated reading it to the very assistant the post says is being targeted.
  The Claude Code active attack didn't stop. 294,842 secrets stolen from 6,943 machines. It evolved and now spreads through Python too and uses Claude Code itself to steal your secrets. The risk to your credentials just got bigger. · p21
• explicitAI-generated volume creates a new quality failure mode distinct from bad code: 'slop' — polished-sounding docs, specs, and messages that people send without having really read, understood, or being able to defend — and this must not be allowed to become normalized just because generation is fast.
  We don't write code anymore · p11

2026-07

• explicit'Workslop' imposes a negative trifecta on recipients — a cognitive tax (confusion, effort to interpret) that cascades into emotional sequelae (frustration, annoyance) that becomes interpersonal judgment (reduced trust in and desire to work with the sender) — so its costs are relational and reputational, not just about wasted time.
  The Hidden Realities of AI Adoption · p8
• explicitcURL ended its long-running bug bounty program in January [2026] because the volume of AI-generated ('AI slop') security reports made running it not worth the mental and time cost to maintainers.
  Who cleans up after the vibe-coding party? · p4
• explicitTreating an AI-assisted documentation project exactly like a high-quality software development process is what let the author get AI's speed without risking a reputation for delivering slop.
  A cautionary tale about AI in tech writing: Why "Trust but Verify" is the only way to scale · p3

2026-08

• explicitAI fatigue (reviewing AI slop, hype exhaustion, being worn down by 'doom trolling' from AI CEOs) is real, and small deliberate acts of withheld participation — e.g. Honeycomb's team-wide no-AI Wednesdays — are a workable way to take back a sense of control.
  Stop being skeptical about AI for development with Charity Majors · p14

2026-09

• explicitAgents are a "fast, honest mirror" of an organization's existing engineering culture: they accelerate good practices into fast, reliable delivery, and just as quickly turn undefined requirements, brittle handoffs, and inconsistent data into unmaintainable code ("AI slop").
  Presentation: From Retrieval to Reasoning: Building Production-Ready Agentic AI Systems with Knowledge Graphs · p3
• explicitdevelopedLines of code is not a valid measure of AI-era productivity: AI's verbosity means more code measures 'slop,' not value, and all else equal, more code is more expensive to maintain and more bug-prone.
  Are You Getting Your Money's Worth from AI? · p11

Tensions

Open gaps (72)

• incompleteNo mechanism for how lived experience becomes transmissible work. The load-bearing premise — that experience filtered through a distinctive voice 'turns into meaning others can access', converting secondhand to firsthand — is asserted but never examined, and the recursion it creates (the reader receiving his transmitted meaning is then holding secondhand experience) is never addressed. This is the essay's central unexamined move and the point where an anti-hype reader will feel the truism.
  The best response to AI slop, infinite advice, and online noise is from Robin Williams — read next: Read the corpus's transmission-problem thread — ki-utvikling-og-folelser (how the next generation acquires craft), you-cant-unit-test-for-taste (where taste comes from / how it transmits) and svenson-attention-real-skill-ai-prompts (names the decisive skill, offers no method) — alongside Polanyi on tacit knowledge (does lived experience transmit at all?). Frame as infrastructure for getting lived experience *through* into distinctive, transmissible work, not as motivation.
• incompleteThe essay is secondhand advice, built on a secondhand fictional artifact, arguing against secondhand material; it survives only by silently reclassifying 'secondhand-through-a-distinctive-voice' as firsthand. That substitution relocates the real claim from 'firsthand experience matters' to 'distinctiveness of perspective matters' — two things that can come apart (and that AI-augmented work might also carry) — but the move is never made explicit or defended.
  The best response to AI slop, infinite advice, and online noise is from Robin Williams — read next: Read on performative / self-referential contradiction and test whether distinctiveness of voice, not novel firsthand experience, is the actual operative variable. Cross with eating-my-own-dog-food (human-originated seed vs prompt-generated framework) and franco-what-we-lose-when-ai-writes (voice as evidence of a Self) to see whether 'voice' can be specified independently of 'lived experience.'
• incompleteFirsthand vs secondhand is treated as a hard binary, but all human work recombines absorbed (secondhand) inputs — everyone's 'little life moments' are themselves saturated with others' content — and AI can also prompt, augment or occasion genuine firsthand experience. The essay admits no continuum and no role for AI as a spur to real experience rather than a substitute for it.
  The best response to AI slop, infinite advice, and online noise is from Robin Williams — read next: Read dawkins-claude-delusion (which flags exactly this sharp mimicry/genuine-experience binary as a weakness) and the taste article; probe where on the continuum 'your own LLM' actually sits, and where AI functions as a prompt for firsthand experience rather than a replacement of it.
• incomplete'It's all art' universalizes the firsthand-experience premium to every kind of knowledge work, colliding with the essay's own art-vs-science distinction (some work is a reproducible search for external truth — explicitly NOT art). The piece never marks where the claim stops applying, leaving an inspiring but unfalsifiable exhortation — a live risk given the creator/marketing register in which it is written.
  The best response to AI slop, infinite advice, and online noise is from Robin Williams — read next: Read Adler on separating a practical exhortation from a testable claim, and ask which categories of work the firsthand-experience premium genuinely governs versus where reproducible correctness — not distinctive voice — is what the audience needs (cf. the taste article's correctness-vs-quality axis, where 'correct' and 'good' come apart in the opposite direction).
• incompleteNo engagement with cost ceilings or economic boundaries. $124-$200 per multi-hour autonomous run is presented as routine; there is no discussion of when this stops scaling (e.g. teams running this 100x/day, regulated environments with per-call cost controls, or comparison to a human contractor at equivalent output).
  Harness design for long-running application development — read next: Read pieces that treat agent-cost economics directly — Simon Willison's pricing analyses, the smallcode argument for smaller models, any IT-procurement perspective. Also: Anthropic's own enterprise pricing docs as the implicit deployment context.
• incompleteNo treatment of audit, observability, governance, or failure containment for long-running autonomous coding. The piece's implicit deployment is 'a single engineer running experiments at Anthropic Labs.' A Norwegian public-sector or regulated context would need: persistent audit trails of each agent's actions and tool calls, rollback semantics for partial builds, secret management when agents access live services, IP provenance of generated code, and human-checkpoint policies. File-based agent communication is actually well-suited to audit — but the author never makes that case.
  Harness design for long-running application development — read next: Read the EU AI Act's high-risk-system requirements, NIST AI RMF agent guidance if it exists yet, and any sober writing on agent observability stacks. Also: cross-reference Anthropic's enterprise-tier compliance docs.
• incompleteThe 'simplify when models improve' methodology assumes monotonic capability advance. It does not address the (empirically real) case where a new model has different — not strictly better — failure modes. E.g. Sonnet 4.5's context anxiety vs. Opus 4.6's regression on some niche tasks. The methodology is silent on what to do when component removal *reveals* a new weakness rather than confirming an old strength.
  Harness design for long-running application development — read next: Look for empirical model-version-comparison work — Aider/SWE-bench longitudinal results, internal Anthropic evals if available, and practitioner accounts of regressions (e.g. Simon Willison's lab notebooks).
• incompleteThe criteria-as-stylistic-steering observation ('museum quality' produces visual convergence) is surfaced and then dropped. It is treated as a quirky finding rather than a serious concern about AI-generated homogenization. At scale, if many teams use Anthropic-suggested criteria, the result is a deep convergence in the look of AI-generated software.
  Harness design for long-running application development — read next: Read on cultural homogenization risk in generative AI (Naomi Klein, Ted Chiang, and design-criticism writing). Also: the 'AI slop' discourse and any empirical work on generated-design diversity.
• incompleteThe 'long-running' threshold is operationalized only through examples (3.8 to 6 hours) — never defined. A reader cannot tell whether the prescriptions apply to a 30-minute task, a multi-day task, or only to the specific case study durations. Böckeler's harness theory and the smallcode piece operate at different time scales without acknowledgment.
  Harness design for long-running application development — read next: Cross-reference extract-bockeler-harness-engineering.json (theoretical-control framing — variety reduction, feedforward, feedback sensors) which is time-scale-agnostic; the smallcode piece's smaller-task framing; and reach for any time-scale-explicit treatment of agent autonomy windows.
• uninformedThe piece is silent on the existence of a broader harness-engineering theoretical literature (Böckeler's adaptive-control framing, the smallcode engineering-instinct view) — even though Anthropic Labs is presumably aware. As a result, named phenomena are coined fresh ('context anxiety') without acknowledging or engaging with adjacent theory. This is not necessarily a mistake — it may reflect the piece's narrow Labs-experiment scope — but it does mean the reader has to do the cross-mapping work themselves.
  Harness design for long-running application development — read next: Maintain the syntopical map (already in this repo as syntopical-harness-engineering-for-ai-coding-agents.json) and treat this article as one empirical data point, not a theoretical contribution.
• incompleteThe DeepSeek piece reports prices and FLOP reductions but does not address the broader geopolitical / supply-chain context — US export controls, the H100/H800 distinction, the question of whether DeepSeek's efficiency gains are partly a forced response to compute constraints rather than pure research progress. The framing is purely technical/commercial.
  DeepSeek v4, and the end of the OpenAI/Microsoft AGI clause — read next: ChinaTalk / Jordan Schneider on US-China AI competition; Dwarkesh Patel interviews with DeepSeek-adjacent researchers; SemiAnalysis on Chinese AI inference economics
• incompleteThe AGI clause obituary documents the legal mechanics but does not interrogate what the original clause was actually for. Was it ever a real safety mechanism (the Charter framing) or always a negotiating chip / PR talking point? The piece presents the dissolution as inevitable without examining whether anyone inside OpenAI ever took the clause seriously as governance.
  DeepSeek v4, and the end of the OpenAI/Microsoft AGI clause — read next: Karen Hao's 'Empire of AI'; Dario Amodei's departure rationale; Ilya Sutskever's Superalignment exit; the actual text of the OpenAI Charter and its drafting history
• incompleteThe LLM 0.32 refactor describes the technical changes but does not address how downstream plugins and users will be affected, beyond noting that previous prompt= calls still work. The migration story for the broader ecosystem (every llm-* plugin, every script that does for chunk in response: print(chunk)) is implicit.
  DeepSeek v4, and the end of the OpenAI/Microsoft AGI clause — read next: The LLM plugin documentation; comparison with how Anthropic, OpenAI, and Google SDKs have evolved their streaming APIs
• unaddressedWillison's newsletter style is to compile signals and let connections emerge implicitly. The three lead stories share a deep unity — commoditization (DeepSeek), legal/conceptual dissolution (AGI clause), and abstraction collapse (LLM refactor) all point at the same phenomenon of AI no longer being the bounded, specialized, frontier-lab artifact it was in 2023 — but the newsletter never makes this synthesis explicit.
  DeepSeek v4, and the end of the OpenAI/Microsoft AGI clause — read next: Ben Thompson's Stratechery on disaggregation; Carlota Perez on technological surges and the transition from installation to deployment phase; Simon Willison's own blog post 'Open Weights = Open Doors' if it exists, or his back catalog on commoditization patterns
• uninformedThe claim that human skills (empathy, ethics, collaboration, judgment) now matter more than code output is attributed secondhand to a single executive recruiter's remark in conversation, not examined against counter-evidence or defined more precisely — it is asserted as received wisdom rather than argued.
  Presentation: Getting Rid of LeetCode Interviews in the World of AI — read next: Primary research on which specific human capacities remain predictive of engineering performance as AI absorbs code production.
• self-assessment biasThe author is grading his own framework by applying it to his own work. There is no external validation, no second writer replicating the quadrant assignments independently, and no reader-side evidence that the framework-guided post is actually stronger than a counterfactual version. The self-referential structure is rhetorically clever but epistemically circular.
  Eating My Own Dog Food: How I Used the Framework to Write the Post About the Framework — read next: Independent case studies applying the framework; A/B testing of framework-guided vs. unguided AI-assisted writing.
• scopeThe demonstration covers exactly one genre (persuasive long-form essay) by one expert writer. No evidence is offered that the quadrant assignments would hold for other knowledge work types -- technical documentation, code review, strategic memos, creative writing -- where risk and differentiation profiles differ.
  Eating My Own Dog Food: How I Used the Framework to Write the Post About the Framework — read next: Apply the framework to diverse knowledge work outputs and check whether quadrant assignments remain stable.
• mechanismThe post does not explain how a practitioner should determine which quadrant a given piece of work falls into. The author's assignments feel intuitive but the decision criteria are not made explicit enough for someone else to replicate them.
  Eating My Own Dog Food: How I Used the Framework to Write the Post About the Framework — read next: The parent post 'Don't Automate Your Moat' may provide the missing decision criteria; worth checking.
• counterfactualNo comparison to what would have happened without the framework. The author asserts the framework guided his delegation decisions, but an experienced writer might have made similar choices by instinct. The framework's marginal value over general editorial judgment is not demonstrated.
  Eating My Own Dog Food: How I Used the Framework to Write the Post About the Framework — read next: Studies on structured decision-making vs. expert intuition in creative/knowledge work.
• incompleteThe adversarial-critic prompt pattern is presented as highly effective but with only anecdotal evidence from one use case. The failure modes of this approach (model sycophancy despite hostile persona, critique that is adversarial in tone but generic in substance) are not explored.
  Eating My Own Dog Food: How I Used the Framework to Write the Post About the Framework — read next: Research on LLM sycophancy and the reliability of adversarial prompting for substantive critique.
• uninformedThe cited 75.33% law-professor preference finding for LLM answers over peer instructors is reported without the students'-side outcome (whether students who received LLM answers actually learned better or worse), the specific sample of contract-law questions used, or which models were tested — details that materially affect how far the finding generalizes beyond 'LLMs write plausible short answers professors like reading.'
  Fragments: July 21 — read next: Read the original Stanford Law study directly for full methodology and any student-learning-outcome measures, and check for replication in other legal or technical education domains.
• incompleteFranco never distinguishes operationally between AI-as-editor and AI-as-author. He gestures at 'co-creator' and 'sparring partner' but offers no test for when LLM involvement has crossed from helping you think to thinking for you. Since the whole prescription hinges on this line, its absence is the essay's central structural weakness.
  What we lose when AI writes for us — read next: Andy Matuschak's notes on evergreen-note writing and 'understanding requires effortful engagement'; Sönke Ahrens, How to Take Smart Notes (the operational case for note-writing as thinking); literature on cognitive offloading (Risko & Gilbert) for empirical traction on which kinds of offloading degrade what kinds of cognition.
• incompleteThe implicit theory of selfhood is constructivist (writing constitutes the Self) but Franco never engages alternatives: that selfhood is constituted in speech (Charles Taylor, dialogical self), in action (Aristotelian), in narrative across many modalities (Ricoeur), or that the 'Self' being expressed by his authorial gallery is a cultivated public persona rather than an inner essence.
  What we lose when AI writes for us — read next: Charles Taylor, Sources of the Self; Paul Ricoeur, Oneself as Another; Sönke Ahrens on writing-as-thinking; and contra: Cal Newport / classical-rhetoric arguments for speech and dialectic as primary.
• incompleteThe argument from stylistic convergence to cognitive convergence is the most consequential claim in the essay and is unsupported. Franco asserts it ('we converge around rhetoric, what happens then?') but provides no mechanism. A Sapir-Whorf-style claim is doing the work uncited.
  What we lose when AI writes for us — read next: Linguistic relativity literature (Lera Boroditsky, Guy Deutscher); studies of LLM influence on user vocabulary and reasoning (e.g., recent work on 'epistemic homogenization' in LLM-assisted writing); Stolen Focus (Hari) on attention-environment shaping cognition.
• incompleteNo engagement with the possibility that LLM-mediated reflection can be MORE rigorous than solo blank-page writing for some people — e.g., neurodivergent users for whom externalized dialogue scaffolds rather than replaces thought; or that writing from a blank page is itself a culturally specific Western Romantic ideal.
  What we lose when AI writes for us — read next: Literature on extended cognition; disability/neurodivergence and AI-assistance; the rhetoric tradition (which privileges dialogue and topoi over solitary blank-page composition).
• illogicalSelf-undermining performance: Franco demonstrates LLM-style techniques 'on his own' (the anaphora caveat) to prove he can do them without an LLM. But this concedes that the techniques themselves are not the marker of AI authorship — humans use them too. If the stylistic tells are not in fact diagnostic, the empirical claim ('humanity's writing style') is weaker than asserted.
  What we lose when AI writes for us — read next: Studies on inter-rater reliability of human/AI text detection; the history of these rhetorical figures (which long predate LLMs).
• uninformedThe essay treats LLM-induced stylistic homogenization as historically novel. Prior waves of stylistic dominance (AP style, MBA-speak, SEO writing, business-jargon, Strunk-and-White) produced their own convergences without producing the cognitive collapse Franco fears — suggesting style-to-thought transmission may be weaker than claimed.
  What we lose when AI writes for us — read next: History of plain-style movements (Orwell, 'Politics and the English Language'); style guide history; sociolinguistics of register convergence.
• incompleteSame system-shift-framed-as-practice-tweak pattern recurring across the user's recent extractions (Cutler, Osmani, Reed, HBR Career-Growth-Overwhelmed). Duffy diagnoses a structural failure of the manager layer to keep pace, then prescribes individual behavior changes that leave organizational architecture, role boundaries, decision rights, and compensation untouched.
  Managers Are Struggling to Keep Up with the AI Productivity Boom — read next: Pair with Cutler 'AI Won't Save the Kingdoms We Built' and Osmani 'Orchestration Tax is You' for the syntopical thread. The unanswered question: when is the manager role itself the bottleneck-design, and what would an AI-era org chart actually look like?
• incompleteTreats manager decision-rights over AI-produced output as unproblematic — but if AI generates faster, broader, and (with verification) better output than the manager's review can keep up with, the manager's authority is conventional, not epistemic. The piece never asks whose judgment is actually load-bearing.
  Managers Are Struggling to Keep Up with the AI Productivity Boom — read next: Cathy O'Neil on algorithmic accountability; Bainbridge 'Ironies of Automation' for what happens to operator authority when automation outpaces oversight (Paul Reed extract).
• incompleteThe AI-as-EQ-coach example is presented as a clever augmentation, but if managers cannot find time for warm communication, that's an org-design failure being masked by a tool. The article never asks whether normalized DM-auditing by AI changes the implicit contract between manager and report.
  Managers Are Struggling to Keep Up with the AI Productivity Boom — read next: Surveillance/trust literature; HBR 'On Managing Yourself' for the older norm being replaced.
• illogical'Increase frequency to course-correct faster' (daily syncs) is offered as a remedy for manager overload, but adding meetings to an already overloaded manager is the textbook overload-amplifier. Osmani's orchestration-tax argument applies to managers too.
  Managers Are Struggling to Keep Up with the AI Productivity Boom — read next: Cutler TBM on institutionalized overload; Osmani 'Orchestration Tax is You'.
• incomplete'89% of leaders agree AI has accelerated work' — but the article assumes that acceleration is sustained throughput rather than a transient burst as teams adopt new tooling. No engagement with the possibility that the 'AI productivity boom' is a one-time S-curve, not the new steady state.
  Managers Are Struggling to Keep Up with the AI Productivity Boom — read next: DORA reports on AI's effect on engineering throughput; longitudinal AI-adoption studies.
• incompleteThe flywheel/S-curve/liminal frame is used to describe both the NAV transformation (which succeeded) and the AI shift (in progress). The conversation never names a transformation that failed at the liminal phase and asks why — so the framework is at risk of being unfalsifiable on its own terms.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Read failed transformations through the same frame — e.g., government-IT projects that died in their liminal phase, large agile adoptions that reverted. Cutler's overload work and the 'people who tried Spotify model' literature would expose where the frame breaks. The Geoffrey Moore 'Crossing the Chasm' tradition has more developed accounts of curves that stall.
• incompleteThe 'learning vs production' rule is stated as a personal heuristic but not connected to any educational theory or empirical evidence. For a leader of consultants asked to scale this practice, there is no model for how the two modes should be partitioned, whether across days, projects, or moods.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Donald Schön's reflection-in-action; deliberate-practice literature (Ericsson); Beck's 'tidy first?' framing of preparatory vs delivery work — the tidy/messy split echoes the learning/production split structurally. Worth syntopical pass against Beck's recent 'Starving Genies' work on AI-assisted craft.
• incompleteThe elevator metaphor is generalised from Jonas's own career and from the show's animating premise. The conversation does not seriously consider organisations where vertical traversal is structurally suppressed (military, regulated finance with information walls, classified environments). The implicit premise that elevators are always available may not hold.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Read about organisations with designed information barriers — security classifications, MAR-walled investment banking, healthcare compartmentalisation. James C Scott's 'Seeing Like a State' on legibility. Where the elevator is locked, what substitutes?
• incompleteThe introvert-leader claim rests on one practitioner's experience and one rhetorical contrast (scale removes small-talk tax). Jonas notes that some colleagues found it hard to distinguish his opinions from his decisions — a cost that may be specifically introvert-shaped (lower social-cue density) but is not investigated.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Susan Cain on introvert leadership; the Cutler thread on 'signals that look like decisions' in leadership communication. The implicit problem of 'low-cue leadership at scale' is worth its own extraction.
• incompleteThe tractor and car analogies argue for slow structural change, but neither is examined for disanalogies. AI compresses learning loops in a way physical machinery cannot. The argument relies on the assumption that adoption is gated by humans, not by capability — which is plausible but not defended.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: The general-purpose-technology economics literature (Bresnahan & Trajtenberg); David Autor on labour-market restructuring time. Counter-cases: dial-up to broadband transitions, mobile phones — both moved faster than tractors. What predicts speed?
• uninformedThe Gukesh anecdote is reported confidently ('the only one of the young players not allowed a computer before age 12') but is not actually verified in the conversation. Whether true or apocryphal, it is doing argumentative work it has not earned.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Quick fact-check; more importantly, treat the underlying claim about protected early craft as a hypothesis and look at the actual evidence on AI use in early-career learning — programming pedagogy research will move on this in 2026-2028.
• incompleteThe claim that NAV's success was driven by capability investments is asserted from inside the case by the very people who made those investments. There is no counterfactual — no comparable agency that did not invest similarly and failed similarly. Some of the 'flywheel' may be storytelling.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: Compare cross-country COVID welfare-IT responses (Germany, Denmark, UK), and Norwegian agencies of similar size that did not transform similarly. The Skatteetaten and Helsedirektoratet experiences would be a natural comparison.
• illogicalJonas argues both that we are early on the AI S-curve (so 10% gains are not the story) and that complexity will push back on productivity gains as they accumulate. These are compatible but in tension: if the curve climbs steeply because of intent-level abstraction, the complexity ceiling should appear later; if complexity bites soon, the curve is shallower than claimed. The argument is not adjudicated.
  17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis — read next: The Brooks / Mythical Man Month tradition on accidental vs essential complexity; Ousterhout on system design; recent measurements on long-running agent harnesses (Anthropic harness design work) which directly test the complexity-ceiling claim.
• incompleteMethodological (the study's own thinnest point): 'social listening' on public posts is a convenience sample of vocal, self-selecting users. There is no denominator, no correction for selection bias, and no way to distinguish frequency-of-posting from frequency-of-use — so a ranking of what people TALK ABOUT online is presented as a ranking of what people DO, and emotionally charged uses (therapy, grief, romance) that generate more posting are structurally over-weighted. The order-of-magnitude larger dataset improves precision but not representativeness.
  How People Are Really Using AI in 2026 — read next: Read the author's own 'Making sense of research on how people use AI' (HBR, Nov 2025) alongside survey- or telemetry-based usage studies (e.g., first-party Anthropic/OpenAI usage reports) to triangulate the social-listening picture against a representative sample and quantify the selection bias.
• incompleteConsumer/individual usage is used to reason about enterprise value: the dataset is 'mostly individuals... at home and at work,' yet the business transformation verdict is drawn from it. Individual bottom-up use and organizational value are different units and are conflated, which both flatters adoption breadth and muddies the value verdict.
  How People Are Really Using AI in 2026 — read next: Read extract-who-cares-about-consumer-ai (the ~100x per-user token-economics split between consumer and enterprise) and enterprise-specific ROI studies to keep consumer-scale adoption separate from organization-level value realization.
• uninformedThe thinkslop harm is asserted at population scale from vivid single-user anecdotes. The study measures the prevalence of use cases where thinking COULD be outsourced (a quarter of top uses) but not the cognitive damage actually incurred, and — crucially — it presents the sharpening 'sparring-partner' use from the same data without ever quantifying the crutch-vs-foil ratio, so the headline concern rests on an unmeasured mix.
  How People Are Really Using AI in 2026 — read next: Read the cited 'cognitive debt' study (arXiv 2506.08872, 'Your Brain on ChatGPT') and extract-cognitive-surrender (offloading vs. surrender, posture-dependence, the 73% wrong-answer acceptance finding) for the mechanism and the controlled evidence the HBR piece substitutes anecdote for.
• incompleteThe captured article cuts off mid-way through 'Technique 7: Remove AI tells' behind a paid-subscriber paywall ('This post is for paid subscribers'); the technique's content and any concluding wrap-up are unavailable to this reader.
  How to turn your AI into a world-class designer — read next: Check Anshu Chimala's own Substack for a non-paywalled or later-unlocked version of the full piece before treating the technique list as complete.
• incompleteThe article never reconciles its headline framing ('built in three prompts,' 'built in two prompts') with the seven distinct named techniques it goes on to describe — it's unclear how many techniques were actually stacked to produce the opening hero demos, or what the realistic cost/iteration/wall-clock budget of the full pipeline is for a team that isn't the author.
  How to turn your AI into a world-class designer — read next: Treat 'N prompts' claims skeptically until technique count and iteration count are reconciled; look for a follow-up or reader Q&A addressing total cost.
• incompleteThe essay is entirely of the print-essay era: it says nothing about digital, collaborative, or AI-assisted writing. Its whole model — a single author revealing a single self to a reader — does not touch what 'sounding like yourself' or 'style as self-revelation' mean when text can be machine-generated, co-written, or stylistically homogenized at scale.
  How to write with style — read next: Read against Franco 'What we lose when AI writes for us' (style/voice as the Self, and its convergence under AI), Acunzo 'The best response to AI slop' (distinctive firsthand voice as the non-commoditizable signal), and the taste article (correctness vs. quality when a machine produces the prose).
• incompleteThe blanket-ban policy treats all AI-assisted contributions identically regardless of whether the human contributor understands and can defend the change, yet Kelley's own 'laundering' complaint implies maintainers can already detect disguised AI use in practice — raising the question of why a graduated policy (require and verify genuine understanding, rather than excluding by origin) wouldn't achieve the same quality/trust goals without a categorical exclusion. The interview doesn't address this alternative.
  Andrew Kelley Interview: Why He Built Zig, Banned AI Contributions, and Moved Zig off GitHub — read next: Compare with other open-source projects' disclosure-and-review policies for AI-assisted contributions, to see whether detection-plus-accountability achieves comparable outcomes to a blanket ban.
• incompleteThe article never quantifies what fraction of Zig's actual pull-request volume was AI-related before the ban, so the scale of the problem the policy was designed to solve is asserted, not measured.
  Andrew Kelley Interview: Why He Built Zig, Banned AI Contributions, and Moved Zig off GitHub — read next: Zig's own GitHub/Codeberg issue-tracker history or maintainer commentary quantifying pre-ban AI-contribution volume.
• incompleteThe paradox is asserted but its mechanism is under-specified. Shipper offers 'every agent needs a human' (a maintenance claim), 'benchmarks miss prompting' (an attention claim), and 'models commoditize yesterday's competence' (a frontier claim). These are three different mechanisms doing different work, and Shipper conflates them. The maintenance claim is explicitly transient — he concedes personal agents return as models improve. The attention claim is partially circular — he will redesign his benchmark to zero out a saturated model. Only the frontier claim is structural, and it is the least developed. A serious version of the thesis needs to argue that the new frontier work is itself non-automatable and remunerated — neither is shown.
  The AI paradox: More automation, more humans, more work | Dan Shipper — read next: Acemoglu & Restrepo on task displacement and reinstatement; the 'augmentation vs. automation' literature (Brynjolfsson, Mitchell); recent econometric work on AI's effect on call-centre and software-engineering productivity (the GitHub Copilot RCT, Brynjolfsson-Li-Raymond on generative AI in customer support)
• incompleteThe 'humans-as-orchestrators' vision is unfalsifiable in this conversation. Shipper says explicitly that when models 'saturate' his senior-engineer benchmark, he will redesign it to zero out the current model. If the benchmark moves to wherever AI cannot yet go, the claim 'humans are still needed' is true by construction and tells the listener nothing about the actual trajectory of automatable knowledge work. A senior engineering leader needs a falsifiable formulation — what specifically would need to be true for Shipper to concede that the 'more humans' claim has expired? — and the conversation does not offer one.
  The AI paradox: More automation, more humans, more work | Dan Shipper — read next: Popper on falsifiability; Sutton's 'bitter lesson' as the counter-frame; the eval-design literature (HELM, MMLU saturations, the ARC-AGI debate); recent critiques of human-baseline benchmarks (Anthropic's METR work on long-horizon agentic tasks)
• incompleteSelection effects in the Every case are uninterrogated. Every is ~30 self-selected curious early adopters with pre-release model access, dual media-and-software business model, founder writer-CEO, no legacy systems, no regulated environment, no enterprise sales process longer than the model release cycle. Every assertion in the conversation is sourced from this one organization and projected onto knowledge work in general. For evaluating organizational impact in a Norwegian enterprise context (regulated industries, slower procurement, less English-language model access for non-English work, strong worker-council constraints), the generalization gap is large and unflagged.
  The AI paradox: More automation, more humans, more work | Dan Shipper — read next: Erik Brynjolfsson's recent work on cross-firm productivity dispersion in AI adoption; Wharton-led surveys on enterprise AI deployment; case studies from regulated EU firms (Klarna's published numbers and their later retraction); Norwegian-context: BI Handelshøyskolen / Sintef studies on AI adoption in Nordic enterprise (the 'forskning og digitalisering' extraction in this library)
• incompleteToken-economics assumption (SaaS users bring their own tokens via Codex) is treated as a stable equilibrium when it is more plausibly a transitional artifact. Once enterprise procurement notices that token spend is shifted to user-attached agent harnesses, three forces will push back: (a) per-call agent-tier pricing from SaaS vendors capturing the new volume, (b) enterprise consolidation of agent infrastructure (corporate-controlled Codex/Claude Code deployments), and (c) usage-based SaaS pricing emerging precisely to capture agent-driven volumes. Each of these inverts Shipper's 'buy SaaS stocks' conclusion. He does not engage any of them.
  The AI paradox: More automation, more humans, more work | Dan Shipper — read next: Tomasz Tunguz's recent essays on AI pricing; the cloud-pricing history (AWS's evolution from flat to consumption); Bessemer State of the Cloud reports on agent-driven pricing changes; OpenRouter / LLM-aggregator economics
• incompleteShipper's 'CEO must be personally AI-pilled' claim sits uncomfortably with his 'super-agent per company maintained by a forward-deployed engineer' claim. If the FDE is the load-bearing role and the per-company agent is the substrate, the CEO's personal model fluency is arguably the wrong variable to optimize — the firm needs FDE talent supply and an org design that protects FDE attention from the C-suite. The conversation never reconciles the personal-fluency prescription with the structural FDE prescription.
  The AI paradox: More automation, more humans, more work | Dan Shipper — read next: Karl Weick on 'sense-making' in organizations; recent CIO/CTO surveys on AI organizational placement (Gartner, MIT Sloan); the literature on 'two-pizza team' analogues for AI deployment
• incompleteNo engagement with worker-attention costs of the prescription. 'Ride the models' for every new release, 'try Codex in your off-hours if your employer blocks it', 'every agent needs a human gardener', 'inbox-zero for 10 straight days via Codex monologue' — collectively this is a maximally attentive lifestyle marketed as liberation. Shipper notes he 'works way more' and frames it as paradox-evidence, not as cost. For a senior engineering leader thinking about sustainable organizational design, the elision of attentional and psychological cost is significant.
  The AI paradox: More automation, more humans, more work | Dan Shipper — read next: The 'AI psychological costs' extraction in this library (extract-psychological-costs-of-ai-*); Cal Newport on attention residue and deep work; recent labour-economics work on AI-driven work intensification (LSE, Stanford); union/works-council positions on AI workload
• illogicalThere is internal tension between (a) 'CLIs are over, GUIs win' and (b) 'agents using SaaS via CLI is how SaaS survives'. If the user's primary surface is Codex/Co-work GUI and the agent talks to SaaS over CLI, then CLIs are precisely what is preserved — they are the agent-readable API layer, not the user surface. Shipper conflates the user-surface CLI claim with the agent-readable-API CLI claim. The two are different and have opposite trajectories: the first dies, the second flourishes. The conversation does not separate them.
  The AI paradox: More automation, more humans, more work | Dan Shipper
• incompleteThe tailwind thesis rests on the empirical claim that audiences will reliably prefer authentic/human content over polished synthetic content at scale, but no mechanism or evidence is offered. Mosseri simultaneously concedes Instagram is 'not very good at ranking AI content yet' and that as models improve it 'might lose the ability to detect' AI content — so the very provenance-labeling and ranking that the strategy depends on may be unworkable, leaving the tailwind under-defended.
  Adam Mosseri: AI is a tailwind for authenticity — read next: Empirical work on engagement with labeled AI vs. human content and parasocial/authenticity preferences; the AI-slop discourse on how telltale synthetic output degrades information ecosystems; whether 'the person behind the content' is a durable ranking signal.
• incompleteNo discussion of maintenance burden. Protodash depends on Cursor rules, an MCP server for Sail, and bundled components — all of which must track a living design system. The article does not address the ongoing cost of keeping these synchronized.
  This week on How I AI: The internal AI tool that's transforming how Stripe designs products (Protodash at Stripe)
• unaddressedNo evidence beyond Stripe. The argument generalizes from a single company with an unusually mature design system, high quality bar, and engineering-heavy culture. It is unclear whether the approach transfers to companies with less-formalized design systems.
  This week on How I AI: The internal AI tool that's transforming how Stripe designs products (Protodash at Stripe)
• unaddressedThe 'demos not memos' framing does not address when prototyping is premature — situations where the strategic question is whether to build at all, not what to build. Prototypes can anchor thinking on implementation details too early.
  This week on How I AI: The internal AI tool that's transforming how Stripe designs products (Protodash at Stripe)
• incompleteNo discussion of prototype fidelity confusion. When prototypes look production-quality, stakeholders may mistake them for shippable code, creating misaligned expectations about engineering effort still required.
  This week on How I AI: The internal AI tool that's transforming how Stripe designs products (Protodash at Stripe)
• unaddressedThe newsletter is a curated summary of a podcast interview, meaning the extraction is working from a secondary source. Nuance, caveats, and context from the original conversation may be lost in summarization.
  This week on How I AI: The internal AI tool that's transforming how Stripe designs products (Protodash at Stripe)
• uninformedAll reported practice comes from one senior, well-resourced team (10+ years' experience each) at a company absorbing roughly $2,000/month per engineer in AI spend; the piece generalizes 'the review bar cannot drop' and 'months of coaching to get good engineers up to standard' as achievable expectations without addressing whether less senior, less resourced, or more cost-constrained teams can sustain the same review intensity, or what happens to engineers who never built hand-written-code intuition in the first place.
  We don't write code anymore
• illogicalO'Reilly draws an explicit analogy between AI-assisted writing and AI-assisted coding ('writing with AI might well follow the same arc as coding') without addressing an obvious disanalogy the article itself surfaces: Gene's coding system was recoverable because it had a 'battery' — an automated test suite that could verify whether Opus's work was correct — while prose has no equivalent automated verification, so the safety net that made the coding case recoverable may simply not exist for writing.
  Stranded in the Slow Zone — read next: Read alongside discussions of verification/evaluation infrastructure for creative or non-code AI output, and alongside the corpus's existing AI-slop material.
• evidentiaryNo quantitative evidence is offered for any of the enumerated harms. The 'net negative' claim rests entirely on an unweighted list of negatives versus two positives.
  The growing AI backlash
• dialecticalNo engagement with counterarguments: productivity gains in knowledge work, medical applications, accessibility tools, scientific research acceleration. The piece treats these as non-existent rather than as insufficient to offset harms.
  The growing AI backlash
• predictiveThe political prediction (2028 elections) lacks any mechanism story — how does diffuse frustration convert into voting behavior or policy change?
  The growing AI backlash
• constructiveThe closing hope that 'some future form of AI might be great' is unconnected to any analysis of what would make future AI different from current GenAI.
  The growing AI backlash
• incompleteThe article gives no quantitative sense of the actual scale or trend of AI-generated versus human contributions across open-source projects generally -- it relies on anecdote (Stenberg, Ruiz, van Rossum) and a single economic-modeling paper (Koren et al.) rather than data on what fraction of pull requests to major projects are now AI-assisted, or whether the influx is accelerating, plateauing, or already being absorbed by improving detection and tooling.
  Who cleans up after the vibe-coding party? — read next: GitHub's own aggregate PR/commit provenance data, or academic studies quantifying AI-assisted contribution share over time across large samples of repositories.
• misinformedThe opening hook's claim that reading the article digitally (via a browser) necessarily means 'you have just used' cURL overstates cURL's role in that specific pathway -- most mainstream web browsers use their own networking stacks rather than libcurl to fetch web pages, even though cURL genuinely is extremely widely embedded elsewhere (package managers, command-line tools, embedded devices, app backends). The framing conflates cURL's real, vast reach with a specific, likely inaccurate claim about browser page-loading.
  Who cleans up after the vibe-coding party? — read next: cURL's own documentation on where libcurl is and isn't actually used (browsers vs. tooling vs. embedded systems) for a precise picture of its footprint.
• incompleteThe 'Trust but Verify' framing itself is a well-worn pattern already pervasive in AI-adoption writing (borrowed from the Reagan-era arms-control phrase and repeated near-verbatim across countless similar LinkedIn/AI-adoption pieces). What is genuinely more specific here is not the slogan but the mechanism underneath it: a concrete 5-stage pipeline with named, checkable tools (Prettier, markdownlint-cli2, custom static analysis, Vale with a custom dictionary, the BMAD method, @kayvan/markdown-tree-parser) and an explicit spec-to-client-doc translation cascade. A reader already saturated with 'trust but verify' framings should judge this piece on whether that tooling/mechanism is reusable, not on the slogan, which adds no new information by itself.
  A cautionary tale about AI in tech writing: Why "Trust but Verify" is the only way to scale — read next: Compare against other AI-adoption pieces the reader has already logged with the same 'trust but verify' framing to see whether any of them supply comparably concrete, named tooling rather than just the aphorism.
• illogicalThe essay's own practice is not obviously exempt from the problem it describes: it is itself a credible-looking piece of content (citations, footnotes, historical erudition) written by an author who elsewhere admits using Claude 'to help me editorialize and think through my ideas,' and its closing line ('Maybe ask Claude?') jokes past, rather than resolves, whether AI-assisted argumentative writing should be gated or trusted any differently than the AI-generated bug reports or papers it condemns.
  You Probably Won’t Read This Article…and That’s OK — read next: extract-franco-what-we-lose-when-ai-writes takes the harder version of this same self-exemption question head-on (whether AI-assisted writing degrades authorial selfhood/credibility).
• incompleteNo discussion of the platform/trust risk of automating a personal LinkedIn account — bot-detection or ToS risk on the platform side, or the reputational cost if an audience later discovers a 'personal voice' account was substantially AI-run — the piece frames automation as a pure production-efficiency question.
  Zero to Agent in 30 Minutes: Build a Hermes Social Media Agent with Craig Hewitt — read next: The corpus's authenticity-premium concept (rising audience demand for verifiably human signal as synthetic content grows abundant) and ai-slop discussions of AI-generated-content detectability bear directly on the risk this piece never raises.