We have bought apple developer enterprise accounts for 5 years, $20,000, please contact us if you have.
This interview summary of IOS development is short and has no answers to the interview questions, just a few words for non-trained iOS developers like me.
I had a video interview for the first time in my life yesterday. I had a total of IOS development and three hours of technical interviews, but I haven't met the personnel, so I should be dead.
However, the whole process down the feeling is quite a lot, in addition to feel the interviewer's ox X, but also know that they usually in the study of the deficiencies.
First of all, let me introduce some difficult questions in the interview:
If you were to implement the weak attribute, how would you do it?
If you were to implement atomic IOS development properties, how would you do that?
Why do you want to create a subclass to implement KVO?
The composition of the class structure. What does the ISA pointer point to?(Metaclasses and root metaclasses should also be mentioned here.)
How many event sources does a RunLoop have?How many modes are there?
What is the data structure of the method list?
How is the classification implemented?Why does it override the original method?
It's also worth mentioning that I asked about my own blog (JSONModel parsing, EOC notes) etc..
This interview made me deeply realize two points and IOS development:
For every design, you should not just "know how to use it," you should understand how to implement it, and almost every design is related to data structures. Understanding data structures and Pointers will help you understand these designs.
After you understand how design works, you also need to understand why: Why do you design this way?It is also a good idea to know what is the flaw in the design that is not present in any design that solves a similar problem?
The first is a question of "how" and the second is a question of "why", while I'm sure many people stop at "what" and "using".
During the interview, I strongly felt the interviewer's capability of the deep: give me feeling, for him, almost all of the design can be explained in some kind of data structure (sometimes also can combine pointer), understanding of knowledge point and IOS development very clear: even if is very simple knowledge, also can say so many things to deep.However, I have just started to learn data structure, so I almost have no idea when it comes to the problem of data structure.
What I want to say:
Therefore, I think for the majority of non-professional iOS developers, if they want to go far in the development of iOS, they must supplement basic computer knowledge such as data structure, algorithm, pointer as soon as possible, otherwise it will form a great resistance to the understanding of knowledge.Once you know the IOS development and basics, you'll be able to understand each technical point more deeply and learn other languages more effectively in the future.
In a nutshell: programmers first, iOS programmers and IOS development second.Only in this way of thinking can the road become wider, faster and farther.
With iOS development in such a bad state, it's understandable that the market would want to filter out people with weak computer knowledge.
The so-called "bad" now is only bad relative to the "abnormally good" before.Now the industry is "bad" because it is getting better, and we should be happy.
So for those of us (non-trained iOS developers), it's important to be aware of the dangers ahead, not to mention that the rain has already come.