I think The Verge said it the best. Taking advantage of these tools to the maximum requires you to have "software brain" which the average person does not have. They struggle to set up a simple automation in their smart home platform of choice. There is little reason to believe they will take the leap to use such tools to simplify daily tasks because it requires people to think about which daily tasks can be simplified and automated.
Apple's culture is such that everything is in Radar. EVERYTHING. It doesn't get done if it's not in Radar.
Positive: Everything is searchable. It is organizational history going back decades. The company is built around this tool.
Negative: The importance of such a tool goes unrecognized compared to the criticality of the system to Apple as a whole. So when it's slow or breaks, everyone is having a bad day.
It takes a really special person who hasn't gone through a CS education to be aware that when faced with a problem that have an obvious solution, they realize that there are things they don't know and either seek out resources to learn them or identify people that can ask for help beyond a simple "I'm stuck, solve this for me!" response.
And that's why of you're a good software engineer, your job is secure. Because most people definitely aren't that and just end up making a real mess of things.
I recently went through an MS phone interview and didn't do as well as I would have hoped. I did learn quite a bit though. Here's my advice:
1) Actual programming and a technical interview are not and never will be the same thing. Assume you know nothing. And I do literally mean nothing.
2) Start with a basic intro to programming book in a language you aren't familiar with and try to do simple tasks in a language you already know. This simulates a bit how it feels to program under pressure. Things you know you know seem not to come out quite as quickly. This helps to emphasize point #3.
3) Practice. Practice. Practice. Practice. Practice. A decent chunk of your typical interview questions exist out there. I'm not saying to memorize them, but be familiar with their solutions. Eventually you'll get to the point that an approach for solving a new problem will come from pieces of old ones.
4) Since coding is done on whiteboards, do not use a compiler. Pencil and paper.
5) Find someone to give you an honest-to-goodness mock interview.
Honest question as a developer looking eventually to move to the Valley in a year or so: is it really that hard to find good people? Is software development really that hard? I taught myself 99% of what I know and found it to be pretty easy, and currently do iOS dev work. Just wondering.
So to say that he owns no part of OpenAI is silly.