The author observes that some software projects, particularly those using AI-assisted coding, exhibit unexpected and chaotic changes, reminiscent of Bruegel's "Tower of Babel." While the biblical story often emphasizes pride, it also highlights the unity essential for technological progress. In the original Babel narrative, humanity's shared language facilitated immense collective power and ambitious projects. God's intervention scattered people and their languages, halting their unified construction efforts.Similarly, AI tools can increase individual developer productivity, enabling more ambitious software creation. However, large software projects are primarily limited by the coordination and shared understanding among developers, not just individual coding speed. This shared understanding, the "language" of a software project, encompasses concepts, boundaries, invariants, ownership, and design rationale, existing through documentation, code, reviews, and conversations.Historically, friction in understanding, though slow, helped synchronize developers by forcing them to learn and agree on system behavior. AI agents, by removing this friction, allow developers to independently make changes without necessarily engaging with others or acquiring a deep grasp of interconnected systems. Consequently, scaled vibecoded projects can become unmanageable, not due to a lack of communication, but the absence of a need for it. Agents act as tireless translators, making local alterations, but this process erodes the shared architectural language necessary for humans to reason collectively. Unlike the biblical Babel where stopped construction signaled the loss of understanding, AI-assisted engineering allows construction to continue even after shared understanding has collapsed, leading to subtle, disorienting progress.