Essential Analysis of Application Conditions and nature of Application Conditions

Essential Analysis of Application Conditions and nature of Application Conditions

Essential Analysis of Application Conditions

Beautiful Life of the sun and fire god (http://blog.csdn.net/opengl_es)

This article follows the "signature-non-commercial use-consistency" creation public agreement

Reprinted please keep this sentence: Sun huoshen's beautiful life-this blog focuses on Agile development and mobile and IOT device research: iOS, Android, Html5, Arduino, pcDuino, otherwise, this blog post is rejected or reprinted. Thank you for your cooperation.

I have been applying for a column for a while, but I have never figured out how to write the corresponding content.

The idea stems from the fact that many developers have such or such limitations during the recruitment process. Especially, for initial requirements, they often write clear content in various blog posts on the Internet, the applicant did not actively participate in the trial, Turning others' things into their own things, to increase the chance of winning the candidates.

In fact, this is what I pay more attention to in the recruitment process. It doesn't matter. What I want to see is:

1. Passive Candidates: whether or not they actively want to understand what they do not understand during the interview process. First, they must put down their dignity and false masks. Second, they must have a positive attitude, this plays a decisive role;

2. Take the initiative to apply for an employee's knowledge of the technical points required for recruitment, or spend at least one or two hours rehearsing, A positive attitude must be matched with positive actions;

3. Whether to treat each other with sincerity during the interview (yes, no, no, it takes half a day in advance to get a tiger skin, which is better than talking to me during the interview, or, it is much more important to care about it, or to answer questions.) It determines whether you need to spend a lot of time managing your work in the future. Simply put, we all have a single shot, which keeps direct leaders confused about your path. The result is never trust. Relatively speaking, I prefer to use an old gun, but it refers to where the gun is shot, otherwise, the management risk coefficient will increase.

First of all, the interview is to let the employer understand the process of your person. Only after this is done, your technical staff will dare to use it. Otherwise, they will take a shot and do not know where to take the shot, or if you don't know where to touch it, the gun will be taken out and you haven't waited for the target!

Then, you will have a general understanding of the overall level, depth, and technical architecture of your technical knowledge.

The key point is that during the interview, you have to say one or two. If not, at least you have not done enough homework before the interview, even if you have spent a few more hours in the interview, it is better than not answering questions during the interview. If you are not sure, you can explain it, then, let's make a brief description of your current degree of understanding. Maybe this description can show your potential.

More is to check whether you are really worth the salary you want during the trial period, and the interview usually requires you to be able to cope with the written examination and interview. (For the written examination, I have very few experiences. Basically, I have moved the examiner into place during the interview. If I really need the written examination, I will explain it clearly, I will take my mobile phone or computer to check the information, because I never remember these things. This is also a habit that was developed seven years ago after a difficult trial, because I need to free up my mind to think about more important things, and excessive details will make your mind sink at this level and cannot rise, let alone the architecture. First, I will study the recruitment conditions and possible scope of the company in advance, and prepare the materials for the mobile phone and review them at any time. Of course, the premise is very important, you have to take the time to practice, or have rich project experience. I use some unknown nouns instead, at least the examiner can understand them)

After talking about this, let's get down to the truth. The content listed in the recruitment conditions is usually divided into two parts, one of which is the characteristics of the language or platform, some of them are the implementation and application of common technologies in the industry in this language or platform.

In the subsequent series of blog posts, we will compare the Java and Objetive-C languages on the Android and iOS platforms.

Some will extract other blog posts, some will write some examples, and other Blog content will also be written as examples.

The content to be mentioned may be more of a foreshadowing, just like an iOS tutorial written three years ago. At the end of the article, I really don't know how to write it or paste the official document, or stick to explain, often think this is a bit silly, it is not desirable. Instead, it is code that can actually run and is the most expressive. This is also the method adopted by most blog posts. I also like to read such a blog post. Of course, the code of a large segment is not as good as the source code, A lot of blog posts written by foreigners have a very simple technical knowledge, which can be clearly written. I want to read it many times. If I have time, I will study it first, start writing the following technical blog posts on recruitment conditions.