Woz at one point talks about how if you don't understand the undocumented instructions maybe they aren't for you. Anyway, kind of nice ambience to it as well.
Officially, but Jobs/Woz were making and selling illegal blue tone boxes 10 years before that around 1972. They allowed you to basically steal phone time from the phone companies by simulating the sounds that nickles/dimes/quarters made when inserting them into a payphone so you didn't have to pay to use the phone for local or long distance calls.
I think we are saying the same thing; it’s a cheeky remark that to read Apple’s documentation is in it of itself, a learned skill, essential to being productive in Swift.
I read the comment as Woz saying documentation isn’t for the faint of heart ... true
(Mind you, I love Apple’s docs now, and honestly prefer it compared to Stripe-y and Twilio-y documentation... to me S&T docs are a style that tries to smooth over the cluttered calls and returns. Are they APIs that makes sense to accomplish x style or job succinctly, or do I have to read the 8 million other things I don’t care about to do the one thing I need to do?)
Ah, ok. No, we weren't saying the same thing, but I now understand what you meant, and I also happen to agree. Current Apple documentation sucks. I think you may be exhibiting some kind of Stockholm syndrome :).
Woz at one point talks about how if you don't understand the undocumented instructions maybe they aren't for you. Anyway, kind of nice ambience to it as well.