Former Apple engineer describes 15-year-old codebases with named ownership and reuse practices

The account describes a development culture where code is treated as a permanent, authored artifact. Each file carried metadata linking it to its original contributor, and modifications to old code often involved direct consultation with the original author. This practice contrasts with modern workflows where code is frequently generated, refactored, or replaced without the same level of traceability. The permanence of the codebase was reinforced by a sense of pride in individual contributions, which were visibly integrated into the larger system.

The reuse of old code was framed as a deliberate practice rather than an exception. When renovating parts of the system, engineers would preserve old components in a reusable state, even if they were temporarily removed. This approach suggests a bias toward stability and incremental improvement, where the cost of rewriting was weighed against the value of existing, battle-tested code. The metaphor of bricks emphasizes modularity and fit, implying that each piece was designed to integrate cleanly with its surroundings.

The shift toward rapid, tool-assisted development is presented as a trade-off. While modern tooling enables faster iteration and more ambitious projects, it may also erode the sense of ownership and craftsmanship associated with long-lived code. The example of AI-generated code introducing unauthenticated APIs highlights the risks of prioritizing speed over scrutiny. For engineers working on systems with long lifespans, the loss of named ownership and deliberate reuse may complicate debugging, auditing, and knowledge transfer.

The cultural implications extend beyond technical practices. The pride in individual contributions described in the post reflects a workplace culture where engineers felt a personal stake in the system’s longevity. In contrast, modern workflows may depersonalize contributions, making it harder to identify who is responsible for specific components. This could affect morale, accountability, and the transmission of institutional knowledge, particularly in large organizations where turnover is high.