My Android Interview Road (quad: Fright)

Life is full of fright, a second or dark clouds looking back but the sky

Life is full of fright, a second, dark clouds, looking back but brighter

Congratulations, I got an offer this afternoon. Beijing treatment is also very good with their good luck to get such a deal is very happy I finally found the work of Android

Morning is also more impatient bar next to the friend received an offer oneself also compare lit but afternoon hr gave me the moment really scared to feel all efforts for this moment as a whole I love this world

Speaking of fright.

The interviewer always likes to scare. This is what I feel in my current experience. Some people are kind but scary!

Scary words are:

1. Are you sure?

2. Do you normally test the code as shown?

3. Are you really sure that it can't be xx?

4. (Roommate experience) or you turn xx direction you this direction xx sample xx like come over to me this line?

Calm down when you're scared. For example, an interviewer asked a question.

Can abstract classes be instantiated?

"Well, obviously not."

Are you sure? Abstract class can also have attributes can have some methods of its functions can be implemented specific functions you really sure can't be instantiated?

At the time of the scene is not familiar with the knowledge point of or uncertain, it is likely to follow the rhythm of the interviewer to say that can be instantiated (the reality will be more frightening to take more examples to refute you)

What we're going to do is calm down and think about it. It's most important to stick to your own thoughts, even if it's wrong.

Again, an abstract class is something that is abstract and conceptually independent of the fact that there is no such thing as an interface that cannot be instantiated.

　　　　

Also like

What is the life cycle of activity when you press the back key? (written in the previous blog post)

He's going to be very serious. You've seen Logcat, didn't you? Is that what you do when you test?

Still have to think about it. Be firm about sticking to your own ideas

There's an example of a language a roommate learns to interview when the interviewer starts from that language and goes to other languages, he asks him very seriously.

You can not turn xx to this turn XX special good such as XX

When my roommate felt a chance, I said yes.

And the interviewer says he's not firm enough to do anything for the money.

In fact, how to answer this question or to think about it or the actual situation is the main

PS: Roommate interview successful 13th roundtable you know

　　　　

There is also an example of a contentview for the speed optimization of the ListView to cache and a viewholder to reduce Findviewbyid repeated load resources

The interviewer will ask you if you think Contentview and Viewholder are better at the optimization of the ListView speed. In other words, who is the deciding factor?

We all know that the cache is the deciding factor, so it's still the same thing. Stick to your thoughts and yell out the Contentview caching mechanism is the deciding factor

　　　　

The previous post to the homepage was rejected by the blog Park--good sad because the length is not enough (I am the original well--this is also knowledge sharing, it seems that the length is not enough)

So write some more today

There are some frequently asked questions.

　　　　

What are the categories of Android animations?

"Tween and Frame" (specifically need to look up some information I particularly headache gestures and animations this piece wants to cry--)

　　　　

MVC pattern, you know?

"Model View Controller mode view Controllers Android is a good way to inherit this pattern from Java (who says it is not possible to fully follow)" (Please check the information for details)

How does the process of view define how the system is drawn in XML? This is the deeper thing.

"Three-step measure layout Draw" (This is also when I came back to remember when the tense did not answer) (specifically, please google)

　　　　

Intent flag (Load mode) You know what it is? What's the difference?

"Singletop Standard Singletask SingleInstance" (http://blog.csdn.net/tiancizhenai/article/details/7037787 introduction more details)

　　　　

Anyway, it's too scary today because the waiting time is very long after three sides. Almost no patience (12-18 days)

At the time, Android engineers asked a lot of Android things only asked a simple two algorithm fast and binary search

Two sides is the algorithm should not understand the Android because I introduced the time he did not know the broadcasting mechanism also asked me to intercept text messages need not root such a problem

What he's asking is that the algorithm compares many puzzles, such as the balance tree list, and so on, I was abused, but I was in three.

Three-side HR test quality I'm going to write a blog about it tomorrow.

　　　　

One second, dark clouds and a look back. Every day is full of hope. This is the life I want.

　　　　

My Android Interview Road (quad: Fright)