One of my mantras that I picked up as I moved into a more senior level is “the fastest and easiest to maintain code is the code you don’t have to write at all”. Knowing when and what to write is as much a skill as writing the code in the first place.
Also, Apple, presumably being a very siloed organization, probably benefits more from tribal knowledge of the elders more than your typical organization.
There's also the pragmatic flip side to this coin. 'Bad' code that does something is infinitely faster than the perfect implementation that was never written.
Also, Apple, presumably being a very siloed organization, probably benefits more from tribal knowledge of the elders more than your typical organization.