Best of Technical Debt — April 2026

1. 1
   Article

   The New Stack·5w

   Who will maintain the web when PHP’s veterans retire?

   A Perforce 2026 PHP Landscape Report surveying over 700 developers reveals a growing skills gap in the PHP ecosystem: more than half of PHP developers have 15+ years of experience, while only 15% have five years or less. Hiring has become the top challenge for PHP team managers, with 24% citing lack of skilled personnel as a leading operational concern. Analysts warn this isn't just a PHP problem but an open source problem, compounded by AI-generated code creating silent technical debt without enough junior developers to manage it. Despite the talent crunch, PHP remains foundational — tied with JavaScript at 72% usage — powering millions of e-commerce sites, WordPress installations, and APIs, mostly at companies with fewer than 500 employees. Symfony and Laravel lead the framework landscape.

   59

   21
2. 2
   Article

   Engineering Enablement·4w

   Cognitive debt: The hidden risk in AI-driven software development

   Dr. Margaret-Anne Storey introduces and expands on the concept of 'cognitive debt' — the erosion of shared understanding across development teams as AI and agentic tools accelerate code production. Unlike technical debt, which lives in the code, cognitive debt lives in people's minds and manifests as lost shared theory of what a system does and why. Drawing on Peter Naur's idea that a program is a theory held by its developers, the post argues that AI-driven velocity can outpace human understanding, leading to paralysis, debugging friction, slower onboarding, and developer burnout. Warning signs include fear of making changes, over-reliance on tribal knowledge, and systems becoming black boxes. Mitigation strategies include requiring human understanding of AI-generated changes before shipping, documenting intent not just changes, regular knowledge-sharing checkpoints, rigorous reviews, and tests that capture intent. A Triple Debt Model is proposed adding 'intent debt' — the erosion of externalized rationale needed by both humans and AI agents — alongside technical and cognitive debt.

   39

   4
3. 3
   Video

   Awesome·6w

   They want mediocre developers...

   A critical take on 'comprehension debt' — the growing gap between the volume of AI-generated code in a system and how much of it developers actually understand. Drawing on a study showing AI-assisted developers performed worse at debugging, and the 2024 DORA report showing higher throughput but increased delivery instability, the argument is that AI coding tools are accelerating code production faster than teams can meaningfully review or comprehend it. The concern extends to a long-term lock-in scenario: AI labs are subsidizing low prices during a customer acquisition phase, and as developers lose critical thinking and debugging skills through over-delegation, they become dependent on tools whose prices could rise dramatically. The post also critiques the incentive structure of AI labs profiting from token consumption regardless of code quality.

   32

   3
4. 4
   Article

   Erik Hazington·3w

   What coding and cooking have in common

   Technical debt and refactoring are explained through a kitchen analogy: a messy kitchen (technical debt) slows down cooking (feature development), while a clean, organized kitchen enables efficient work. Just as restaurants have closing days for cleaning, development teams need dedicated time for refactoring — updating language versions, removing unused code, and cleaning up quick fixes — to keep a codebase maintainable long-term. The analogy is offered as a way to justify refactoring to non-technical stakeholders.

   30

   7
5. 5
   Article

   Harasim.dev·6w

   Glue Work: The Invisible Effort That Actually Ships Products ‣ harasim.dev

   Glue work — the invisible labor of mentoring, refactoring, documentation, and team alignment — is what actually keeps software projects running, yet it rarely appears in Jira tickets or performance reviews. Research suggests up to 50% of technical work is invisible to at least one stakeholder, and teams may spend 40% of their time on unrecorded tasks. Developers who absorb too much glue work risk career stagnation and burnout, while organizations that ignore it accumulate technical debt and hidden capacity loss. The post covers how to shift from 'accidental' to 'intentional' glue through brag documents, reframed communication, async written records, and organizational practices like refactoring budgets, wins channels, and rotational roles. It also surveys engineering analytics tools (Swarmia, LinearB, DX) and AI-assisted PR review tools (CodeRabbit, GitHub Copilot) that can surface invisible contributions automatically. A practical audit checklist and retrospective questions are included for engineering managers.

   15

   2