Best of Agile — April 2026

1. 1
   Article

   Tech Lead Digest·6w

   The Phoenix Architecture

   A veteran software engineer draws parallels between the Extreme Programming movement of the late 1990s and today's generative AI era, arguing that both represent 'rigor relocation' rather than loss of discipline. Just as XP replaced heavyweight processes with tighter feedback loops, and dynamic languages replaced static types with test-enforced correctness, AI-assisted development demands stricter specification of intent and ruthless evaluation of outputs. The core thesis: probabilistic code generation only works when deterministic constraints exist at the edges. Engineers who thrive will treat generation as a capability requiring more precision in specification, not less, and will build evaluation systems that fail loudly when code drifts from intent.

   85

   1
2. 2
   Article

   Manager.dev·4w

   Managing a team that didn't choose you

   An Engineering Manager shares an honest retrospective of his first 6 months taking over an existing team at HoneyBook. He describes three key challenges: abandoning his planned technical onboarding when he discovered the team had been without real management for 6 months and needed people-focused leadership; over-pressuring the team to hit sprint goals without sufficient technical context, leading to burnout and pushback from a senior engineer; and discovering 21 neglected support tickets that required a focused 'hotfixing blitz' to resolve. The core lesson is that rigid 30-60-90 onboarding plans fail in practice — constant adaptation, paying attention to team signals, and willingness to course-correct matter far more than any pre-made plan.

   123

   8
3. 3
   Article

   thoughbot·5w

   Ship faster: How to unlock development speed in regulated industries

   Slow development in regulated industries like healthcare is often a process problem, not a code problem. A consulting team helped a healthcare client overcome waterfall culture by replacing exhaustive PRDs with lightweight, iterable requirements, running design sprints to align stakeholders, mapping cross-team dependencies visibly, and establishing a lightweight coordination structure. The key insight is that change management and political alignment are as important as technical execution when trying to increase development speed.

   30

   2