The first interview after resignation, record the interview questions, check the gaps and fill in the gaps.
1. What project are you working on recently? What is your role in the project?
2, the characteristics of java, inheritance, polymorphism, encapsulation. A deeper understanding, asked me a why use encapsulation? My answer doesn't seem to be the answer he wants
3. Is String an object reference? I said yes, stupid! Then he said that I String a="abc" right? I say no, because "abc" is placed in the character constant area, and then he is the one you know and say yes, me. . .
4. The structure of the set. Collection difference
5. Memory leaks, such as the database connection is not closed, the IO stream is not released, the explanation is the understanding of the stack
6. What else does Spring have besides IOC and AOP?
7. Spring injection method
8. Spring loading process
9. The startup principle of Spring Boot
10. The request process of SpringMVC, some annotation explanations of SpringMVC
11. Talk about your understanding of restful
12. Principle of .properties, inheriting HashTable
13. The loading process of jsp
14. What are the js selectors?
15. The underlying structure of js
16. What are the methods of jquery that are usually used?
17. Principle of ajax Js
18. In addition to the http protocol, which protocols are used, the interviewer said socket, and I don't remember one
19. Do you know webserver?
20. Do you usually use threads? In what scenario is it used?
21. How to resolve thread conflicts? Here's what I'm saying: Do you mean the thread safety aspect? You can use the synchronized keyword, and volatile field modification, and then he said what to do with blocking? A question, if 100 people grab ten tickets, how can you guarantee to buy the tickets?
My first thought was definitely synchronized modification, but I felt that he didn't want this answer, so I asked why there was blocking (personally, it was very funny), he said that synchronized modification would block, and then I said it was because it was always occupied Don't let the resources go? That can be done through lock() and unlock(), because lock is an optimistic lock, lock will detect whether there is a conflict in resources, the conflict will always be requested, and it will be occupied if there is no conflict, and then he shows a satisfied smile (this paragraph is really surprising No risk, I should have said it at the beginning)
22. Know what design principles? Did I say factory pattern? Anyway, I don't understand very well, so I just asked casually, he said no, and then asked if I knew the open/closed principle? When I say I know, I say open to the outside world and close to the inside, but he said you know these things, do you know where the key points are? I'm confused, did I say it's a modification? He said, but what about the specific usage scenarios? Did you use it while developing? Then I got stuck, I thought hard for a long time, said that it means to write a class and try not to modify it? Then use inheritance to extend it, he graciously, continue to say, do you know the single design principle? I quickly nodded and said I knew, and then he told me about the Dependency Inversion Principle. Forgive me, I really don't know much about design principles, so I just don't know. Then he stopped, and here we need to understand.
23. What are the difficult problems encountered at work?
24. Do you know POI?
25. Does hibernate know? I said I was using mybatis at work and he regretted it. Asked something about mybatis
26. The principle of database connection pool?
27. The structure and principle of xml
28. Have you used bootstrap form submission? I said no, and then he said what is written on your resume? I said we only use bootstrap css style,
Then he pointed out that my resume is a misspelling of this word (囧), here I need to know
29. There are still some project problems