Preface
There will never be a right time, and you will always feel that you are either too young, too old, or too busy, or for other reasons. If you are always troubled by not finding the perfect moment, then the perfect moment will never appear.
Ali side
1. Self-introduction, including projects.
2. Have seen which JDK source code and understood which libraries are commonly used.
3. The expansion mechanism of the collection framework HashMap, the principle of ConcurrnetHashMap
4. JVM memory model and gc memory recovery mechanism
5. With classloader structure, can I define a java.lang.String class by myself? Why? Parent agency mechanism.
6. Know which design patterns and what are the 6 design principles? Which design pattern is reflected by each design principle?
7. What books have you read about design patterns? What is the title of the book?
8. What have uml models drawn? What are the relationships between the classes in the class diagram, and what are the differences?
9. Did you use a dashed line when drawing class diagrams in UML? What is this for?
10. Have done application-related performance testing, for example, how to use it in actual projects.
What are related to the concurrency framework?
11. What osgi frameworks do you know?
12Have you ever done jvm memory tuning, how to do it, for example, what tools did you use?
Ali two sides
1. Introduction
2. What source code have you seen
3. How to reflect the design patterns used in the class structure diagram of the java io library
4. Draw how to reflect the design patterns you have designed, draw the structure diagram, and explain.
5. Draw out how to expand the project structure diagram of the structure you made, etc.
6. The principle of primary key id design in database design
7. What tools have been used for jvm memory tuning, and what is jstate used for? How to dump the current thread status?
8. Do you understand the concurrency framework?
9.Classloader's parent agency mechanism
10. Practical experience in JVM tuning of application server, how to do it, and where to use it
11. Where to get the latest information and what forum to visit. What do you think of the latest Swift language
12. Design principles correspond to design patterns
13.Servlet/filter principle configuration
14.ibatis in operation and the role of an attribute
15. What design principles does spring aop use, and what is the automatic injection configuration for?
16.jboss class loader
17.session sharing mechanism
18. What is the most successful thing ever done?
19. What is the biggest dispute?
20. Why do you want to leave and go to Ali
Ali three sides
1. What is the company responsible for now?
2. What is the main purpose of the project?
3. What is the company's management method and project problem feedback mechanism?
4. What are the problems with the serialized id used for serialization in Java?
5. Which ones have OSGi used? What is the structure of the class loader, and how to load a class in one bundle in another bundle?
6. Does nio understand the notification mechanism after blocking?
7. How to draw uml design class diagram, the relationship and difference between classes
8. How does spring load bean definitions without configuration files? It may ask for automatic annotations or properties files to define beans
9. Are frameworks such as ibatis actually in use, technical details
10. Why do you want to leave?
Ali all around
1. Introduction
2. What the company does, business, responsible content, reporting mechanism
3. Enterprise-level application security related
4. http protocol, return code, difference between 301 and 302
5. What has been used in multithreading
6. Application server related, talk about the most familiar
7. Why leave
basis
In terms of basics, my suggestion is one super-strong, that is, one or a few small places are particularly proficient, but the breadth must be wide, do not blindly pursue mq these things, the actual interview is still based on (408-computer composition) + database Mainly, that is to say, when your os, network, and database are still good, you have already met the needs of entering a large factory. If you are familiar with two well-known middleware, you can go to harvest. Things like service can easily break your mentality. In fact, my database has a solid theoretical knowledge because I read the Nuggets booklet and the innodb storage engine during the period of confusion, but my os is very poor. I can only talk about the basics of process thread memory, but I still have Some small offers, so everyone must not be greedy. In addition, I only understand Java in the language direction. Some small suggestions are that Java development should be able to pull all the problems of os to the virtual machine and concurrency. In addition, the source code of Java does not necessarily follow the spring, but the collection under juc and util. You must have an understanding, especially what is the first line of the source code for Ali and the like, and you must remember.
In addition, you can remember ideas similar to double verification, and don’t memorize it by rote. For example, the class loader of the virtual machine should not just read books. In fact, the source code is very simple. It may only take half a day for you to go from endorser to source code. Big brother, you must go in for many things, don't observe them outside.
Here are some source notes for everyone, I think it is very helpful to myself.
Due to the excessive number of words in the notes, the notes have been sorted, packaged and compressed into documents. Friends who need it, please help the editor forward (so that more people can see) private message reply [ notes ] to get the notes for free How to get it!
Concurrent programming core notes (must see)
Concurrent programming sharing model articles
- Concurrent programming overview
- Process and thread
- Java thread
- Shared model management
- Shared model memory
- Shared model without lock
- Immutability of the shared model
- Tools for sharing models
Mode articles
Application
Principles
JVM from entry to enchanted notes
- JVM memory area division
- JVM execution subsystem
- Garbage collector and memory allocation strategy
- Write efficient and elegant Java programs
- Performance optimization
- JVM common interview questions guide
MySql performance tuning
- MySQL common objects
- MySQL architecture, storage engine and SQL optimization
- MySQL cache, parameter adjustment and lock
- MySQL common tools, master-slave replication and comprehensive cases
Prepare for Autumn Recruitment Database
Friends in need forward it + follow the editor, check the picture at the end of the article, scan the code and add it for free.
resume
My resume is generally screened and it has only been brushed off by Sanqi and Tucson Future, but I actually have very little personal experience, so my suggestion is to write down my education experience. As for cross-examination candidates, you can write about yourself first For master’s majors, and then for undergraduate majors, do not write first, and do not need to set the template. Here is a super resume, which can be set according to your own preferences. When submitting your resume, try to choose the internal push mailbox for the reasons: 1. Fast response, 2. You can use your own resume template. Here I want to emphasize a misunderstanding. For technical posts, resumes are really only useful for preliminary screening. (Many companies still read my Spring Recruitment CV and gave it to me.) This requires that our CV must be subtracted. How about just enough without digging holes for ourselves? I will post my skill stack if I leave it blank here. In addition, the more internship experience doesn’t seem to be the better. I’ve only posted my Meituan internship, plus 2 or 3 small items to embellish it, and then it’s ready for delivery. , Don’t write too much to dig holes for yourself, most interviewers still face the resume.
project
In terms of projects, I believe it is a difficult point for many cross-examination party and undergraduate students. Here I suggest the video class of Niuke. This is easy to find and does not take a long time. Every half day for a month is enough. I think the most important thing is the project. Completeness is about going through the main process of the project, and then digging in a certain module, that is, digging for your own skill points instead of finding skill points according to the project, for example, when you introduce a cache module, you naturally try The various APIs of redis make it easy to familiarize yourself with the project. In fact, the most important thing in the interview process is why the whole project is designed like this. It is good to answer a few specific points, and deliberately create some bugs and try Some solutions, basically with some such thinking, can find a good internship, and then come into contact with real projects during the internship process. The most important thing for real projects is to straighten out and connect, because what you need to be responsible may be just a certain For specific modules, if you neglect to think and only focus on the implementation of the interface, it is easy to fall into the vicious circle of addition, deletion, modification and investigation.
However, the importance of the project to students is far less important than the foundation. A solid foundation is enough to find a good job. Don't miss a big job. The project is only for the realization of some basic details, and its technical points are far inferior to the book. The above is so in-depth, the important thing in the project is actually some trade-offs for specific business scenarios in the comparison process between various APIs and various middleware, so the most important thing is the basics. I hope everyone will not pay too much attention to the project. If you really don’t have a project, you can follow a complete project in an introductory lecture or a Niu Ke. If you work hard, you can finish it in more than a month, and then you can just think carefully.
Interview
I don’t know if everyone hates interviews like me at first, but I like interviews very much now and I am willing to go to interviews. Because the interview is the most autonomous of all links, we must first have a certain degree of confidence: let me come to the interview, as long as my resume is true, then it proves that my rigid conditions meet the company's requirements. Then the interview should be a process of equal communication. At first, I was prone to stage fright, but later I found that stage fright was upside down. Everyone should pick up their own confidence and guide the interviewer into their field of expertise during the interview. If you find that you are not good at a field, you must have breadth. In other words, there must be at least one of breadth and depth: When you have a particular point, you should pay attention to how to let the interviewer discover you. When you know every point, but not very deep, you should do more divergent guidance. Generally speaking, if you have prepared well, you will have more or less highlights of your own. During the interview, you must remember that the other party is also willing to communicate with you the technology stack and ideas of the current graduates. Every programmer is also For a lonely person, the interview is also the process of making friends. When you feel that the other person is willing to be friends with you, the interview may be over.
Well, today’s sharing is over. Friends who are interested in learning and improving in depth, please check the picture below, scan the code to add, or reply to [Ali] by private message to enjoy massive learning materials! ! !
