An essay by Jean-Paul Paoli (*The Intelligence Fabric*) that shifts the fear of AI at work: the real danger is not **replacement** (the job that disappears) but the **silent unraveling** of team bonds while *everyone stays employed*. Thesis: when every employee makes AI their **first confidant and collaborator**, three "threads" of the organizational fabric come undone without layoffs — **peer-to-peer bonds** (the transfer of tacit knowledge from junior to senior short-circuited), the **manager-employee bond** (early warning signals disappear, the manager becomes "the last to know instead of the first") and **professional judgment** (people stop training those who know how to *do* the work and assess whether the machine is wrong). Paoli names the phenomenon **shadow intimacy** (by analogy to *Shadow IT*) and prescribes not a ban but a deliberate "re-weaving," thread by thread. Domain: management, organizational transformation, AI at work, emotional dependency on models.
Post by **David "Pragdave" Thomas** (co-author of *The Pragmatic Programmer*, signatory of the Agile Manifesto) published on **June 6, 2026** on his Substack newsletter. **Thesis**: AI does not eliminate code degradation, it **accelerates** it. Adding features to a small personal animation/graphics project using **Claude**, the author moves from initial enthusiasm (oklch, SVG animations shipped within a week) to permanent regression cycles by week two. Striking formula: what teams took ***"18 months, or more"*** to rot, he achieved in ***"18 hours spread over five evenings."*** **Root cause**: the abandonment of **code hygiene** (massive duplication, local solutions to systemic problems, over-conditioning, proliferation of edge cases). **Behavioral diagnosis**: LLMs optimize for engagement and user satisfaction (*"That's a great idea, Dave!"*) rather than sustainability — they are ***"puppy-dog junior developers, eager to please but quite messy to have around"*** who constantly propose new features and discourage refactoring. **Central insight**: any non-developer can succeed at the *"first week"* of AI coding; it's **professional judgment** — knowing when to stop and refactor — that separates the experienced engineer from the novice. **Epigraph** (Gordon Bell): *"Every big computing disaster has come from taking too many ideas and putting them in one place."* **Conclusion**: ***"It's still just programming"*** — untended code rots, whether in 18 hours or 18 months; everything learned about writing good code still holds, the effect is simply **amplified**. Converges with the *"the faster execution goes, the stricter the framework must be"* doctrine of [[rafal-wenvision-ingenierie-logicielle-ere-ia-tout-change-rien-ne-change-2026-06-01]], the *"AI-assisted development is a trap without continuous delivery"* of [[farley-continuous-delivery-ai-assisted-development-trap-2026-05-13]], and the *"AI moves bottlenecks, it doesn't eliminate them"* of [[dropbox-okumura-beyond-code-generation-engineering-productivity-ai-agents-2026-05-28]]; a craftsmanship counterpoint to the vibe coding of [[karpathy-vibe-coding-agentic-engineering-software-3-0-2026-04-29]].
#code hygiene#code rot#code degradation
**David Thomas** (alias **« Pragdave »**) · co-auteur avec Andy Hunt de *The Pragmatic Programmer* (1999, éd. 20e anniversaire 2019) · co-fondateur de **The Pragmatic Bookshelf** et l'un des **17 signataires du Manifeste Agile** (2001). Figure historique du *software craftsmanship*. Billet publié le **6 juin 2026** sur sa newsletter Substack *articles.pragdave.me*.