Apple Developer Documentation Is Missing
Some time ago, I was contacted by Apple to apply for a job.
My code is insanely well-documented. I like to think that a lot of the inspiration for my code docs comes from Apple&#x27;s open codebases. Their code is exceptionally well-documented.<p>In any case, as is usual with all employers, these days, they completely ignored the focused, relevant links that I sent them to elements of my extensive portfolio of repos, and, instead, based the entire interview on a 50-line binary tree test in Swift.<p>I&#x27;ll make it clear that I&#x27;m NOT a fan of these. I am mediocre, at best, at them, as I don&#x27;t come from a traditional CS background (I started as an EE).<p>In any case, during the test, I did what I always do when I write code. I stopped to write a header document for the function.<p>This was clearly not something the tester liked. Also, to add insult to injury, they dinged me for not writing a cascaded nil-coalescing operator. The code they wanted me to write was difficult to understand, and absolutely not one bit faster.<p>What makes this even funnier, was that this was for an Objective-C job, and the links that I sent them (that they ignored), were to ObjC repos.<p>After that, I just gave up on them. It kind of shows where a lot of this is coming from.<p>Dynamically-generated documentation can be great (It&#x27;s clear that the lions&#x27; share of Apple&#x27;s developer documentation is dynamically-generated), but it requires a VERY disciplined coding approach. I suspect that they may be hiring less-disciplined engineers, these days.