"Back to the Basics. Recursion." — Daniel Beach (Data Engineering Central)
Why this is in the vault
Daniel Beach's continuing "old curmudgeon vs. the AI agents" thread — this issue is a fundamentals refresher on recursion (recursive CTEs solving a Bill-of-Materials multi-level part explosion in SQL Server, plus the classic self-calling-function example in Python) framed explicitly as a rebellion against "being dumbified by our constant use of AI." He directly addresses an AI agent by name ("a reminder to Lord Claudius that we humans can indeed rage against the machine when required"), which is unusually on-the-nose for an RDCO vault note about an operator running a Claude-based COO agent.
Mapping against Ray Data Co
Direct hit on the founder's own agent-architecture posture, not a new idea — another data point in an existing tracked tension. [[2026-03-25-seattle-data-guy-know-nothing-and-be-happy]] already named this as "the exact pattern RDCO is built around — an engineer outsourcing code production to AI agents." Beach's piece is the same critique from a different voice in the same corner of the niche: pick a boring, fully-understood technique (recursion — recursive CTEs, BOM explosion) and manually re-derive it as inoculation against "pea-brain turn[ing] into mush" from agent over-reliance. The technique itself (recursive SQL for multi-level BOM/part hierarchies) is a real, reusable pattern for any client work touching hierarchical/parent-child data models — worth keeping as a fundamentals reference even independent of the AI-skepticism framing.
This also chains directly with his own August polemic — [[2026-08-24-data-engineering-central-cheap-code-polemic]] and the guest-post [[2026-04-27-data-engineering-central-luddite-ai-rant]] — confirming this is a recurring editorial lane for the sender (not a one-off), which raises Beach's standing as a tracked voice on the skill-atrophy side of the debate RDCO has to keep answering for its own agent-delegation model.
No new mapping surface, medium strength: thin technical content (recursion 101, no novel implementation detail beyond "here's a BOM problem and a toy Python example"), and the RDCO-relevant argument (does agent delegation atrophy the founder's own technical fundamentals) is already filed and answered elsewhere. This note exists mainly to keep the recurring-editorial-lane pattern visible and to bank the recursive-CTE/BOM technique as a fundamentals reference.
The core argument
Recursion is a fundamentals concept Beach argues engineers are at risk of forgetting under constant AI-agent use. His worked example: a Bill-of-Materials problem (a smartphone's parts, each made of sub-parts, indefinitely nested) is the canonical real-world case requiring recursion — he's solved it with recursive SQL in production. He closes with a minimal Python illustration of a self-calling function and a warning that recursion, handled incorrectly, can spiral like an inescapable loop.
Related
- [[2026-03-25-seattle-data-guy-know-nothing-and-be-happy]]
- [[2026-08-24-data-engineering-central-cheap-code-polemic]]
- [[2026-04-27-data-engineering-central-luddite-ai-rant]]
- [[2026-05-06-osmani-cognitive-surrender]]