{"id":5826,"date":"2026-04-15T12:38:16","date_gmt":"2026-04-15T12:38:16","guid":{"rendered":"https:\/\/www.europesays.com\/ai\/5826\/"},"modified":"2026-04-15T12:38:16","modified_gmt":"2026-04-15T12:38:16","slug":"zendesk-says-ai-makes-code-abundant-shifting-the-bottleneck-to-absorption-capacity","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ai\/5826\/","title":{"rendered":"Zendesk Says AI Makes Code Abundant, Shifting the Bottleneck to \u201cAbsorption Capacity\u201d"},"content":{"rendered":"

Zendesk recently argued that generative AI has changed the limiting factor in software delivery<\/a> from writing code to what it calls “absorption capacity”. Absorption capacity is the organisational ability to define problems clearly, integrate changes into a broader system, verify that they behave correctly, and turn implementation into dependable value. In the company’s framing, once code becomes abundant, the main challenge is no longer producing it quickly but ensuring that rapid generation does not outrun architectural coherence, review capacity, and delivery flow.<\/p>\n

In a post on Zendesk Engineering, Bence A. T\u00f3th<\/a> builds the argument through analogies from agriculture and manufacturing. He argues that improving one part of a system does not necessarily increase total throughput if another constraint remains in place. In software, he writes, generative AI has lowered the cost of producing code enough that implementation is no longer the narrowest constraint.<\/p>\n

\"\"

\nReimagining Margaret Hamilton<\/a>\u2019s iconic Apollo software photograph, when code production remained the primary constraint on software delivery (source<\/a>)<\/p>\n

T\u00f3th\u2019s term “absorption capacity” covers the work required to convert generated code into reliable outcomes. That includes deciding what should be built, aligning implementation with the surrounding architecture, establishing confidence through verification, and determining whether the resulting change actually improves customer outcomes.<\/p>\n

The article proposes four practical responses. First, problem framing should become a shared responsibility between product and engineering rather than a one-way handoff, because ambiguous requirements can now produce plausible but misaligned implementations at scale. Second, teams should lower the cost of confidence by strengthening verification loops, including CI signals, static analysis, security checks, observability, staged rollouts, and rapid product feedback after deployment.<\/p>\n

Third, architecture and engineering conventions should serve as scaffolding for AI-assisted delivery, with clear boundaries, consistent naming, templates, lightweight Architecture Decision Records<\/a> (ADRs), and guardrails enforced in CI. Finally, teams should measure throughput rather than output, favouring metrics such as lead time, review queue time, change failure rates, rollbacks, and incident load over lines of code, pull request volume, or token counts.<\/p>\n

AI, he argues, will scale whatever structures already exist in the codebase and delivery workflow. In systems with clear module boundaries, documented invariants, and a small number of well-understood implementation paths, AI can accelerate work while remaining easier to direct and verify. In systems with ambiguous conventions or architectural drift, the same acceleration can amplify inconsistency, increase review burden, and weaken trust in changes that may look locally correct while degrading the system more broadly.<\/p>\n

In a recent InfoQ news item on Agoda\u2019s view of AI coding tools<\/a>, Agoda similarly argued that coding was never the real bottleneck, and that specification and verification become more important as implementation accelerates. Zendesk pushes that argument further by naming the replacement constraint and framing it as an organisational design problem: how to increase a team\u2019s ability to absorb rapid change without degrading architecture or delivery quality.<\/p>\n

For architects and engineering leaders, the implication is that the advantage may not go to teams that generate the most code, but to those that can safely absorb more meaningful change.<\/p>\n","protected":false},"excerpt":{"rendered":"Zendesk recently argued that generative AI has changed the limiting factor in software delivery from writing code to…\n","protected":false},"author":2,"featured_media":5827,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[24,640,504,5068,25,505,223,966,5069,5067],"class_list":{"0":"post-5826","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ai","8":"tag-ai","9":"tag-ai-assisted-coding","10":"tag-architecture-design","11":"tag-architecture-decision-records","12":"tag-artificial-intelligence","13":"tag-culture-methods","14":"tag-generative-ai","15":"tag-netflix","16":"tag-software-development-lifecycle","17":"tag-zendesk-absorption-capacity"},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/5826","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=5826"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/5826\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/5827"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=5826"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=5826"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=5826"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}